SAP HANA to Synapse
real-time replication
TwinCommit replicates SAP HANA to Azure Synapse Analytics in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to feed Synapse with live SAP HANA data for analytics, AI and reporting, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Synapse
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 Synapse
Micro-batches are staged as Parquet in Azure Data Lake Storage, loaded with COPY INTO and applied with MERGE in one transaction together with the checkpoint. Tables are created hash-distributed on the primary key.
Requirements
- ✓An ADLS Gen2 staging container
- ✓A service principal or managed identity with db_ddladmin and db_datawriter
- ✓ADMINISTER DATABASE BULK OPERATIONS for COPY INTO
Setup
Set up SAP HANA → Synapse 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 Synapse
Add a target block for Synapse. 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: synapse
server: acme-dw.sql.azuresynapse.net
database: replica_dw
auth: managed_identity
staging: abfss://staging@acmelake.dfs.core.windows.net/twincommit/
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Synapse replication FAQ
How does TwinCommit replicate SAP HANA to Synapse?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Synapse in commit order. Micro-batches are staged as Parquet in Azure Data Lake Storage, loaded with COPY INTO and applied with MERGE in one transaction together with the checkpoint. Tables are created hash-distributed on the primary key.
Does SAP HANA to Synapse 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 Synapse replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Synapse 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 Synapse today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.