MariaDB to Synapse
real-time replication
TwinCommit replicates MariaDB to Azure Synapse Analytics in real time by reading the MariaDB transaction log and applying every committed change exactly once and in commit order. Use it to feed Synapse with live MariaDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MariaDB
log reader
commit-ordered · exactly-once
Synapse
native writer
How capture works on MariaDB
TwinCommit reads the row-based binary log as a replica using MariaDB GTIDs, and follows Galera cluster failover automatically.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓REPLICATION SLAVE and BINLOG MONITOR grants
- ✓log_slave_updates on Galera nodes
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 MariaDB → Synapse in four steps
- 1
Prepare MariaDB
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full 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: mariadb
dsn: ${SOURCE_DSN}
server_id: 4201
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]MariaDB to Synapse replication FAQ
How does TwinCommit replicate MariaDB to Synapse?
+
TwinCommit reads changes from the MariaDB 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 MariaDB to Synapse replication need triggers or capture tables?
+
No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.
Is MariaDB 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 MariaDB versions are supported?
+
MariaDB 10.6, 10.11, 11.x · Galera Cluster · SkySQL · Amazon RDS for MariaDB.
Stream MariaDB to Synapse today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.