SAP HANA to Redis
real-time replication
TwinCommit replicates SAP HANA to Redis in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to keep a Redis cache exactly in sync with SAP HANA, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Redis
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 Redis
Each row is written as a Redis hash (or JSON document) under a key template such as `orders:{ORDER_ID}`, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Requirements
- ✓A key template per table
- ✓ACL user with write access to the key prefix
- ✓TLS endpoint recommended
Setup
Set up SAP HANA → Redis 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 Redis
Add a target block for Redis. 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: redis
url: rediss://cache.internal:6380
key_template: "{table}:{pk}"
format: hash
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Redis replication FAQ
How does TwinCommit replicate SAP HANA to Redis?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Redis in commit order. Each row is written as a Redis hash (or JSON document) under a key template such as orders:{ORDER_ID}, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Does SAP HANA to Redis 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 Redis replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redis 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 Redis today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.