SQL Server to SAP HANA
real-time replication
TwinCommit replicates Microsoft SQL Server to SAP HANA in real time by reading the SQL Server transaction log and applying every committed change exactly once and in commit order. Use it to migrate or continuously mirror SQL Server into SAP HANA with zero downtime, with no triggers or capture tables on the source.
SQL Server
log reader
commit-ordered · exactly-once
SAP HANA
native writer
How capture works on SQL Server
TwinCommit reads the active and backed-up transaction log directly, so you do not need SQL Server Agent CDC jobs or change tables.
Prerequisites
- ✓FULL recovery model
- ✓Primary key on each replicated table
- ✓VIEW SERVER STATE and db_owner on the source database
How apply works on SAP HANA
Array UPSERT and DELETE statements committed in the same transaction as the TwinCommit checkpoint.
Requirements
- ✓log_mode = normal
- ✓Technical user with LOG ADMIN and CATALOG READ
- ✓Primary keys on replicated tables
Setup
Set up SQL Server → SAP HANA in four steps
- 1
Prepare SQL Server
Run twincommit check. It verifies full recovery model and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at SAP HANA
Add a target block for SAP HANA. 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: sqlserver
dsn: ${SOURCE_DSN}
target:
type: saphana
host: hana.internal:30015
user: ${HANA_USER}
password: ${HANA_PASSWORD}
schema: REPLICA
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SQL Server to SAP HANA replication FAQ
How does TwinCommit replicate SQL Server to SAP HANA?
+
TwinCommit reads changes from the SQL Server transaction log, buffers them per transaction, and applies each committed transaction to SAP HANA in commit order. Array UPSERT and DELETE statements committed in the same transaction as the TwinCommit checkpoint.
Does SQL Server to SAP HANA replication need triggers or capture tables?
+
No. TwinCommit reads the SQL Server log directly and creates no objects in the source database.
Is SQL Server to SAP HANA replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same SAP HANA transaction as the data, so a crash or restart never loses or duplicates a transaction.
What SQL Server versions are supported?
+
SQL Server 2016–2025 · Azure SQL Managed Instance · Azure SQL Database (target).
Stream SQL Server to SAP HANA today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.