Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/247208

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:13, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

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

Article ID: 247208

Article Last Modified on 3/14/2006


  • Microsoft SQL Server 7.0 Standard Edition

This article was previously published under Q247208

BUG #56239 (SQLBUG_70)


In a merge publication, there are two different ways to define a conflict:

  • Column level conflict


  • 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.


This behavior occurs due to the use of the custom Stored Procedure Resolver.


Use the default Priority based resolver or custom COM object resolver instead of the Stored Procedure Resolver.


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.

Additional query words: column row level conflict merge replication resolver

Keywords: kbbug kbfix KB247208