SAP HANA to Databricks
real-time replication
TwinCommit replicates SAP HANA to Databricks 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 Databricks 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
Databricks
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 Databricks
Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Requirements
- ✓A SQL warehouse or all-purpose cluster
- ✓A Unity Catalog volume or external location for staging
- ✓A service principal with MODIFY on the target schema
Setup
Set up SAP HANA → Databricks 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 Databricks
Add a target block for Databricks. 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: databricks
host: adb-1234567890.12.azuredatabricks.net
warehouse: replication-wh
catalog: main
schema: replica
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Databricks replication FAQ
How does TwinCommit replicate SAP HANA to Databricks?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Databricks in commit order. Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Does SAP HANA to Databricks 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 Databricks replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Databricks 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 Databricks today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.