Solved

Conflict Resolution for Merge Replication

Posted on 2011-03-17
2
418 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35164081
0
 
LVL 10

Accepted Solution

by:
TAB8 earned 500 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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

In this article I will describe the Detach & Attach 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.
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

707 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