SAP HANA to Redshift
real-time replication
TwinCommit replicates SAP HANA to Amazon Redshift 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 Redshift 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
Redshift
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 Redshift
Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Requirements
- ✓An S3 staging bucket and IAM role for COPY
- ✓A database user with CREATE on the target schema
- ✓Network path to the cluster or workgroup endpoint
Setup
Set up SAP HANA → Redshift 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 Redshift
Add a target block for Redshift. 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: redshift
host: analytics.123456789.us-east-1.redshift-serverless.amazonaws.com
database: dev
staging_bucket: s3://acme-twincommit-staging
iam_role: arn:aws:iam::123456789012:role/twincommit-copy
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Redshift replication FAQ
How does TwinCommit replicate SAP HANA to Redshift?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Redshift in commit order. Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Does SAP HANA to Redshift 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 Redshift replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redshift 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 Redshift today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.