SQL Server to Redis
real-time replication
TwinCommit replicates Microsoft SQL Server to Redis in real time by reading the SQL Server transaction log and applying every committed change exactly once and in commit order. Use it to keep a Redis cache exactly in sync with SQL Server, with no triggers or capture tables on the source.
SQL Server
log reader
commit-ordered · exactly-once
Redis
native writer
How capture works on SQL Server
TwinCommit reads the active and backed-up transaction log directly, so you do not need SQL Server Agent CDC jobs or change tables.
Prerequisites
- ✓FULL recovery model
- ✓Primary key on each replicated table
- ✓VIEW SERVER STATE and db_owner on the source database
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 SQL Server → Redis in four steps
- 1
Prepare SQL Server
Run twincommit check. It verifies full recovery model 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: sqlserver
dsn: ${SOURCE_DSN}
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]SQL Server to Redis replication FAQ
How does TwinCommit replicate SQL Server to Redis?
+
TwinCommit reads changes from the SQL Server 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 SQL Server to Redis replication need triggers or capture tables?
+
No. TwinCommit reads the SQL Server log directly and creates no objects in the source database.
Is SQL Server 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 SQL Server versions are supported?
+
SQL Server 2016–2025 · Azure SQL Managed Instance · Azure SQL Database (target).
Stream SQL Server to Redis today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.