Oracle to Synapse
real-time replication
TwinCommit replicates Oracle Database to Azure Synapse Analytics in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed Synapse with live Oracle data for analytics, AI and reporting, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
Synapse
native writer
How capture works on Oracle
TwinCommit parses online redo and archived logs directly, including RAC threads, and reassembles transactions in SCN order before they leave the host.
Prerequisites
- ✓ARCHIVELOG mode
- ✓Minimal plus primary-key supplemental logging
- ✓Read access to V$ views and the archive destination
How apply works on Synapse
Micro-batches are staged as Parquet in Azure Data Lake Storage, loaded with COPY INTO and applied with MERGE in one transaction together with the checkpoint. Tables are created hash-distributed on the primary key.
Requirements
- ✓An ADLS Gen2 staging container
- ✓A service principal or managed identity with db_ddladmin and db_datawriter
- ✓ADMINISTER DATABASE BULK OPERATIONS for COPY INTO
Setup
Set up Oracle → Synapse in four steps
- 1
Prepare Oracle
Run twincommit check. It verifies archivelog mode and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Synapse
Add a target block for Synapse. 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: oracle
database: PRODDB
user: ${SRC_USER}
password: ${SRC_PASSWORD}
target:
type: synapse
server: acme-dw.sql.azuresynapse.net
database: replica_dw
auth: managed_identity
staging: abfss://staging@acmelake.dfs.core.windows.net/twincommit/
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Synapse replication FAQ
How does TwinCommit replicate Oracle to Synapse?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Synapse in commit order. Micro-batches are staged as Parquet in Azure Data Lake Storage, loaded with COPY INTO and applied with MERGE in one transaction together with the checkpoint. Tables are created hash-distributed on the primary key.
Does Oracle to Synapse replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Synapse replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Synapse transaction as the data, so a crash or restart never loses or duplicates a transaction.
What Oracle versions are supported?
+
Oracle 19c, 21c, 23ai · RAC, Data Guard standby, CDB/PDB · Autonomous Database (target).
Stream Oracle to Synapse today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.