August 8, 2012 at 9:11 am
We are trying to accomplish the following:
1.DB1 is merge replicated to many clients running SQL CE
2.DB2 is also merge replicated to many clients running SQL CE
3.DB1 and DB2 are "synchronized" with each other
Step #1 and #2 are easy. It's the third on that we cannot figure out. We have tried merge replication between DB1 and DB2, but it causes tons of data churn, and redundant updates. The Merge replciation between DB1 and DB2 had filters associated to it. Maybe removing those filters altogether would help?...
We have also tried Peer-to-Peer between DB1 and DB2, but we get an error when it tries to update the rowguid column added by merge replication because it has the ROWGUIDCOL property associated to it. Unfortunately, SQL Server won't allow vertical filtering in a P2P topology, so we can't exclude those rowguid columns from the P2P replication.
I can provide more info if needed.
Any help would be greatly appreciated. Thanks!
August 8, 2012 at 11:19 am
Just a thought: could you make DB1 and DB2 part of a cluster and then replicate merge outward from there?
August 9, 2012 at 12:46 am
You can do the synchronization with the help of SQL Delta tool...
Pls check it out....
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply