Hi guys,
I'm having a problem with large numbers of unresolvable conflicts in a merge publication.
A situation has occurred that has introduced a large number of conflicts across multiple tables which are caused by primary key violations. We're using subscriber always wins conflict resolvers, but the conflicts are not being resolved. From my reading of other posts and threads it appears that the conflict resolver CANNOT resolve conflicts arising from primary key violations.
I have also read that turning on "compensate for errors" on the article should cause the problem to rollback, but that is not happening in practise.
What I'm seeing is that the conflicts are re-propagated every sync, causing the msmerge_genhistory table to grow larger and larger, (around 150,000 new rows are being added every hour), which greatly exceeds the amount of replication traffic I am expecting.
It is not feasible to manually go to the subscribers and delete the conflicting data rows as there are far too many subscribers, tables and conflicts to deal with.
Aside from blowing away replication and reinitialising the entire site, what are my options?
I'm having a problem with large numbers of unresolvable conflicts in a merge publication.
A situation has occurred that has introduced a large number of conflicts across multiple tables which are caused by primary key violations. We're using subscriber always wins conflict resolvers, but the conflicts are not being resolved. From my reading of other posts and threads it appears that the conflict resolver CANNOT resolve conflicts arising from primary key violations.
I have also read that turning on "compensate for errors" on the article should cause the problem to rollback, but that is not happening in practise.
What I'm seeing is that the conflicts are re-propagated every sync, causing the msmerge_genhistory table to grow larger and larger, (around 150,000 new rows are being added every hour), which greatly exceeds the amount of replication traffic I am expecting.
It is not feasible to manually go to the subscribers and delete the conflicting data rows as there are far too many subscribers, tables and conflicts to deal with.
Aside from blowing away replication and reinitialising the entire site, what are my options?