FIX: Merge Replication Conflict Viewer Resolves Data Conflicts Incorrectly

This article was previously published under Q300145
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 353492 (SHILOH_BUGS)
SYMPTOMS
The Conflict Viewer may not resolve merge conflicts correctly when you select the Resolve With This Data option. The conflict appears to have been resolved, but if you check the publisher and subscriber, you will see that the "winning data" has not been applied to the publisher or subscriber.
RESOLUTION
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
You can work around this problem in the following ways:
  • If you are using the default priority-based conflict resolver, manually apply the "winning data" change on the publisher side. This "winning data" change will then be propagated to all subscribers.
  • Use custom conflict resolvers, such as stored procedure or COM resolvers that contain logic to perform conflict resolution.
  • Use Microsoft-provided resolvers such as additive, averaging, maximum, minimum, and "subscriber always wins" conflict resolvers.
STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
Properties

Article ID: 300145 - Last Review: 01/16/2015 22:50:02 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB300145
Feedback