July 17, 2008
MySQL to MSSQL Server Replication?
The team I’m working with is in the process of moving from SQL Server to MySQL.
To ease the burden, we need all writes to the new MySQL databases to be replicated back into SQL Server, so that all of our back-end reports and what-not will continue to function. It’s short term, but not shorter than six months.
I can’t find any generic tool online to do this.
I thought about setting up a bridge MySQL instance with triggers that create a message queue, then reuse our existing Java DAOs to do the heavy lifting (they know how to read/write either SQL Server or MySQL). But, that quickly gets invasive and brittle.
My next thought was a lightweight wrapper around the
mysqlbinlog program which does essentially what the MySQL replication threads do: reads a portion of the binlogs, persists its current position, then replays the statements.
Then I thought, “well, if we’re doing that, why not just reuse MySQL’s replication code and build something around that core?”
You can see the hole I’m getting myself into.
Are there better strategies? Are there (free or commercial) tools that can replay replication logs on a MSSQL Server instance?
The lightweight Perl/Python wrapper seems the best solution. Anybody have experience with something like this (for SQL Server or otherwise)?