SAP HANA to SQL Server
real-time replication
TwinCommit replicates SAP HANA to Microsoft SQL Server in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to migrate or continuously mirror SAP HANA into SQL Server with zero downtime, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
SQL Server
native writer
How capture works on SAP HANA
TwinCommit reads the SAP HANA redo log through a log-reader technical user and decodes row and column-store changes, with no triggers or shadow tables in your SAP schema.
Prerequisites
- ✓log_mode = normal
- ✓Technical user with LOG ADMIN and CATALOG READ
- ✓Primary keys on replicated tables
How apply works on SQL Server
Set-based MERGE into BIN2-collated tables with an in-transaction checkpoint.
Requirements
- ✓FULL recovery model
- ✓Primary key on each replicated table
- ✓VIEW SERVER STATE and db_owner on the source database
Setup
Set up SAP HANA → SQL Server in four steps
- 1
Prepare SAP HANA
Run twincommit check. It verifies log_mode = normal and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at SQL Server
Add a target block for SQL Server. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: saphana
host: hana.internal:30015
user: ${HANA_USER}
password: ${HANA_PASSWORD}
target:
type: sqlserver
dsn: ${MSSQL_DSN}
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to SQL Server replication FAQ
How does TwinCommit replicate SAP HANA to SQL Server?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to SQL Server in commit order. Set-based MERGE into BIN2-collated tables with an in-transaction checkpoint.
Does SAP HANA to SQL Server replication need triggers or capture tables?
+
No. TwinCommit reads the SAP HANA log directly and creates no objects in the source database.
Is SAP HANA to SQL Server replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same SQL Server transaction as the data, so a crash or restart never loses or duplicates a transaction.
What SAP HANA versions are supported?
+
SAP HANA 2.0 SPS05+ · SAP HANA Cloud · S/4HANA and BW/4HANA schemas.
Stream SAP HANA to SQL Server today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.