SAP HANA to Snowflake
real-time replication
TwinCommit replicates SAP HANA to Snowflake 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 Snowflake 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
Snowflake
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 Snowflake
Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.
Requirements
- ✓Key-pair authentication for a service user
- ✓A warehouse for the MERGE step
- ✓OWNERSHIP or INSERT/UPDATE/DELETE on the target schema
Setup
Set up SAP HANA → Snowflake 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 Snowflake
Add a target block for Snowflake. 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: snowflake
account: myorg-myaccount
warehouse: REPLICATION_WH
database: RAW
private_key_file: /secrets/sf.p8
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Snowflake replication FAQ
How does TwinCommit replicate SAP HANA to Snowflake?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Snowflake in commit order. Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.
Does SAP HANA to Snowflake 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 Snowflake replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Snowflake 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.
Use cases for this route
Related replication routes
Stream SAP HANA to Snowflake today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.