We're getting difficulty keeping our data synchronized. We've been managing a system on the UNIX machine during the last two decades utilizing a UNIFY Dataserver. There's been a push to maneuver to Microsoft and therefore are now also managing a Microsoft SQL Server 2008 R2 database on our Microsoft network. Certain tables from all of these 2 databases have to stay in sync. Furthermore, the tables requiring to become synchronized follow slightly different table structures.
The Microsoft SQL server operates on a 64bit machine. Unify haven't written a 64 bit ODBC driver for all of us to make use of when attempting to keep the databases synchronized.
I've checked out the potential of using database triggers on Unify which write logs of changes designed to the tables after which FTP the logs and apply the alterations (in order to call web services to use the alterations) , however when a trigger fires and creates a log/calls something, when the transaction is folded back the log still remains.
Does anybody have applying for grants what the easiest method to keep these databases synchronized could be?
Thanks ahead of time
You might like to consider SQL Server Service Broker, http://technet.microsoft.com/en-us/library/bb522893.aspx
The very best equivalent I'm able to think about could be Oracle Streams if you've ever had the chance to make use of that. A large concern though may be that you simply pointed out this Unify database not getting ODBC driver support for 64 bit envioronments (Even more reason you need to abandon Unify altogether).
Just bear in mind that despite claims the 2 won't ever truly be genuine-amount of time in sync. There'll always be a minimum of a small delay.