?
Solved

Conflict Resolution for Merge Replication

Posted on 2011-03-17
2
Medium Priority
?
433 Views
Last Modified: 2012-05-11
All,

I had my first conflict detection with our merge replication setup.  I queried the msmerge_conflict_publicationname_aspolicy table in both publisher and subscriber and found the record that was the loser? This setup is a client subscription (with first to publisher wins).  So the record that "won" was the correct one.

My question is that when I selected to "remove/delete" the conflict from the Conflict GUI, it only removed the conflict record in the publisher table (msmerge_conflict_publicationname_aspolicy); the subscriber msmerge_conflict_publicationname_aspolicy still has the record.

I had to disable my conflict alert I setup b/c this record still exists in the subscriber; I thought that when I "removed/delete" the conflict it would remove the record in both places, but that is not the case.  When I renabled the alert (that monitors conflicts) it still send me an email telling me there is a conflict.

Can someone let me know what needs to be done here?
0
Comment
Question by:jwa082276
2 Comments
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35164081
0
 
LVL 10

Accepted Solution

by:
TAB8 earned 2000 total points
ID: 35168401
Sometimes replication dosent tidy up after its self very well in the repl sys tables
what you could do to fix this quickly is :
1, stop user access to both pub/sub "no data changes
2, from the sub server delete the subscription
3, on the sub server run sp_removedbreplivation 'databasename'  "this will remove the repl sys tables"
4, create a new subscription to the publication and unselect the initialisie option "this will recreate the repl sys tables but wont reimport all the data so dosent take long"

0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
This shares a stored procedure to retrieve permissions for a given user on the current database or across all databases on a server.
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question