SQL Server to MariaDB
real-time replication
TwinCommit replicates Microsoft SQL Server to MariaDB in real time by reading the SQL Server transaction log and applying every committed change exactly once and in commit order. Use it to migrate or continuously mirror SQL Server into MariaDB with zero downtime, with no triggers or capture tables on the source.
SQL Server
log reader
commit-ordered · exactly-once
MariaDB
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 MariaDB
Multi-row INSERT … ON DUPLICATE KEY UPDATE and DELETE batches, committed with the checkpoint in one transaction.
Requirements
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓REPLICATION SLAVE and BINLOG MONITOR grants
- ✓log_slave_updates on Galera nodes
Setup
Set up SQL Server → MariaDB 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 MariaDB
Add a target block for MariaDB. 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: mariadb
dsn: ${MARIADB_DSN}
database: replica
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SQL Server to MariaDB replication FAQ
How does TwinCommit replicate SQL Server to MariaDB?
+
TwinCommit reads changes from the SQL Server transaction log, buffers them per transaction, and applies each committed transaction to MariaDB in commit order. Multi-row INSERT … ON DUPLICATE KEY UPDATE and DELETE batches, committed with the checkpoint in one transaction.
Does SQL Server to MariaDB 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 MariaDB replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same MariaDB 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 MariaDB today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.