SAP HANA to ADLS
real-time replication
TwinCommit replicates SAP HANA to Azure Data Lake Storage in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to land live SAP HANA data in ADLS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
ADLS
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 ADLS
Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Requirements
- ✓Storage Blob Data Contributor on the container
- ✓Hierarchical namespace enabled
- ✓Optional Iceberg catalog (REST or Hive Metastore)
Setup
Set up SAP HANA → ADLS 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 ADLS
Add a target block for ADLS. 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: adls
account: acmelake
container: lake
path: replica/{schema}/{table}
format: delta
mode: merge
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to ADLS replication FAQ
How does TwinCommit replicate SAP HANA to ADLS?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to ADLS in commit order. Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Does SAP HANA to ADLS 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 ADLS replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same ADLS 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 ADLS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.