Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Resolving merge conflicts Expand / Collapse
Posted Friday, April 26, 2013 3:05 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 31, 2013 8:12 AM
Points: 7, Visits: 59
When I ran "View Conflicts", on the Publication, it listed a few conflicts in some tables. I opened it in the conflict viewer and saw what the problem was.

I have one merge publication with one subscriber. It was setup this way to have a continuously updated backup database, with the understanding that if anything happened to the publication database, everyone can be switched to the subscription (and if it was a hardware problem, once the server housing the publisher, the data would be pushed from the subscriber to the publisher).

After I had set it up, I did a few tests on the subscriber database, created some test records to make sure they were pushed to the publisher. This had the effect of creating some conflicts between the two. When I saw the conflict, I knew the record in the publisher was the record to be kept. I deleted the conflicting record in the subscriber, thinking the merge process with push the correct record from the publisher, and that's what happened.

But, when I run the "View Conflicts", it still shows the subscriber record I deleted as being in conflict with the publisher record. How can I get SQL to stop thinking there is still a conflict between the two?
Post #1447176
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse