You are currently offline, waiting for your internet to reconnect

FIX: Custom Stored Procedure Resolver Does Not Log Merge Conflict Correctly

This article was previously published under Q247208
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #56239 (SQLBUG_70)
SYMPTOMS
In a merge publication, there are two different ways to define a conflict:

  • Column level conflict

    -and-

  • Row level conflict
A Column level conflict defines changes made to the same columns as a conflict, and changes to different columns in the same rows will be merged. However, when setting this Column level conflict in merge publication, you can still get a conflict when updating different columns in the same row.
CAUSE
This behavior occurs due to the use of the custom Stored Procedure Resolver.
WORKAROUND
Use the default Priority based resolver or custom COM object resolver instead of the Stored Procedure Resolver.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
column row level conflict merge replication resolver
Properties

Article ID: 247208 - Last Review: 10/22/2013 03:17:55 - Revision: 2.1

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB247208
Feedback