Resolving conflicts en masse in merge replication

[jcaulder]

We have our replication set such that we have to manually resolve conflicts when they occur(very infrequently).

However, last night a colleague attempted to push a snapshot to a new subscriber and somehow one of the tables never populated with data. This table was related to another table which did receive data. This led to a foreign key violation which led to about 9,000 conflicts at our publisher.

Does anyone know of a way to clear all these conflicts other than through the interactive resolver which requires clicking every row and accepting the action already taken? We're not really in the mood to click this button 9,000 times.

I have already deleted the subscriber thinking this would clear up the conflicts but it does not.

We have a SQL Server 2000 publisher with MSDE subscribers.

TIA,

J

 

[jcaulder]

With no responses yet and being in a hurry to resolve this, we used an undocumented method. For those that may have the same issue, I thought I would post what worked for us:

Prerequisites: Number pad on your keyboard
Waiver: Results may vary; perform at your own risk!!


Step 1: Find a piece of tape about 2 inches in length
Step 2: Attach one end to the front right side of the keyboard just below the <ENTER> key on the number pad.
Step 3: Pull the tape tight across the <ENTER> key and attach to the right hand side of the keyboard ensuring that the <ENTER> key is fully depressed.
Step 4: Go to the break room for 8 to 10 minutes or, if an over-achiever like myself, continue working on .NET application or other productive activity.
Step 5: Remove the tape with about 100 conflicts remaining and clear the remaining items manually.


This undocumented method of clearing all conflicts may be on future Microsoft certification tests so take note.

HTH someone,

J
;-)