SAP HANA to MongoDB
real-time replication
TwinCommit replicates SAP HANA to MongoDB in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to serve SAP HANA data from MongoDB at scale without dual writes, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
MongoDB
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 MongoDB
Relational rows become documents keyed by primary key and are written with bulkWrite upserts inside MongoDB transactions, together with the checkpoint.
Requirements
- ✓Replica set or sharded cluster (change streams need an oplog)
- ✓changeStream and find privileges on watched databases
- ✓Pre- and post-images enabled for full before/after values (optional)
Setup
Set up SAP HANA → MongoDB 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 MongoDB
Add a target block for MongoDB. 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: mongodb
uri: ${MONGODB_URI}
database: replica
document_id: primary_key
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to MongoDB replication FAQ
How does TwinCommit replicate SAP HANA to MongoDB?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to MongoDB in commit order. Relational rows become documents keyed by primary key and are written with bulkWrite upserts inside MongoDB transactions, together with the checkpoint.
Does SAP HANA to MongoDB 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 MongoDB replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same MongoDB 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 MongoDB today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.