Repair a broken Replication Sql Server 2005 vs Sql Server 2008 – PART 2
NOTE OF CAUTION: In the end we decided to turn off the continue on conflict option, because too many conflicts were ignored and the tables got too far out of sync... So the continue on conflict is not such a great option afterall...
Part 1: http://bloggingabout.net/blogs/dries/archive/2009/04/18/repair-a-broken-replication-sql-server-2005-vs-sql-server-2008.aspx
So here's the update: The option to to continue on conflict works fine!
I tested it on two virtual machines that have p2p replication with a test table. Stopped Replication by stopping the SQL agents and then inserted identical rows at all servers. Nothing happened, at least no error.
So I did it again with records with the same id, but different values. That also worked, but the first processed command was replaced by the second value. So both nodes were in sync again.
I decided to go live with it and inserted the missing records from one node in one of the others. No problems at all!
A note of caution though: Not all conflicts are handled.
On Friday I marked a table for replication that did not exist on the other nodes. This did result in a replication error! Apparently the option doesn’t work for this situation. Well, no worries. I created the table on the other nodes and then the magic option did the rest: lots of conflicts, but no errors! Don’t forget to remove the table from the articles of the publication though…
NOTE OF CAUTION:
In the end we decided to turn off the continue on conflict option, because too many conflicts were ignored and the tables got too far out of sync... So the continue on conflict is not such a great option afterall...