SAP HANA to GCS
real-time replication
TwinCommit replicates SAP HANA to Google Cloud 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 GCS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
GCS
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 GCS
Changes land as Apache Iceberg, Delta Lake or Parquet tables with one atomic commit per micro-batch. Iceberg tables register in the BigLake metastore so BigQuery can query them in place.
Requirements
- ✓Storage Object Admin on the bucket
- ✓BigLake Admin for catalog registration (optional)
- ✓Workload identity or a service-account key
Setup
Set up SAP HANA → GCS 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 GCS
Add a target block for GCS. 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: gcs
bucket: acme-lake
path: replica/{schema}/{table}
format: iceberg
catalog: { type: biglake, project: acme-analytics }
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to GCS replication FAQ
How does TwinCommit replicate SAP HANA to GCS?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to GCS in commit order. Changes land as Apache Iceberg, Delta Lake or Parquet tables with one atomic commit per micro-batch. Iceberg tables register in the BigLake metastore so BigQuery can query them in place.
Does SAP HANA to GCS 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 GCS replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same GCS 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 GCS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.