跨不同服务器同步不同数据库类型
我们很难保持数据同步。 过去 20 年来，我们一直使用 UNIFY 数据服务器在 UNIX 机器上运行系统。我们一直在推动迁移到 Microsoft，现在还在我们的 Microsoft 网络上运行 Microsoft SQL Server 2008 R2 数据库。这两个数据库中的某些表需要保持同步。此外，需要同步的表遵循略有不同的表结构。
Microsoft SQL 服务器在 64 位计算机上运行。 Unify 尚未编写 64 位 ODBC 驱动程序供我们在尝试保持数据库同步时使用。
我研究了在 Unify 上使用数据库触发器的可能性，它写入对表所做的所有更改的日志，然后通过 FTP 传输日志并应用更改（或调用 Web 服务来应用更改），但是当触发器触发并写入时日志/调用服务，如果事务回滚，日志仍然保留。
有人知道保持这些数据库同步的最佳方法是什么吗？
预先感谢
格兰特
We are having difficulty keeping our data in sync.
We have been running a system on a UNIX machine for the last 20 years using a UNIFY Dataserver. There has been a push to move to Microsoft and are now also running a Microsoft SQL Server 2008 R2 database on our Microsoft network. Certain tables from these 2 databases need to remain in sync. Additionally, the tables needing to be synchronized follow slightly different table structures.
The Microsoft SQL server runs on a 64bit machine. Unify have not written a 64 bit ODBC driver for us to use when trying to keep the databases in sync.
I have looked at the possibility of using database triggers on Unify which write logs of all changes made to the tables and then FTP the logs and apply the changes (or to call web services to apply the changes) , but when a trigger fires and writes a log/calls a service, if the transaction is rolled back the log still remains.
Does anybody have any ideas on what the best way to keep these databases in sync would be?
Thanks in advance
Grant
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可能需要研究 SQL Server Service Broker，http://technet.microsoft。 com/en-us/library/bb522893.aspx
我能想到的最好的等效工具是 Oracle Streams（如果您有机会使用它）。不过，一个大问题可能是您提到的这个 Unify 数据库不支持 64 位环境的 ODBC 驱动程序（这也是您应该完全放弃 Unify 的原因）。
请记住，尽管有人声称两者永远不会真正实时同步。总会有至少轻微的延迟。
You might want to look into SQL Server Service Broker, http://technet.microsoft.com/en-us/library/bb522893.aspx
The best equivalent I can think of would be Oracle Streams if you have ever had the opportunity to use that. A big concern though might be that you mentioned this Unify database not having ODBC driver support for 64 bit envioronments (All the more reason you should abandon Unify altogether).
Just keep in mind that despite claims the two will never truly be real-time in sync. There will always be at least a slight delay.