PRB: Custom Stored Procedure Resolvers Don't Fire When Conflict Involves UPDATE and DELETE (291263)


The information in this article applies to:

  • Microsoft SQL Server 7.0
  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q291263

SYMPTOMS

In SQL Server merge replication, when the same row is updated at one location and deleted at another, custom stored procedure resolvers defined for the article are not fired. Instead, the default priority-based resolver is fired. Custom stored procedure resolvers are fired, however, for conflicts between updates to the same row at different locations.

CAUSE

This behavior is by design.

WORKAROUND

As a workaround, you can develop a custom COM resolver for SQL Server.

MORE INFORMATION

For additional information, consult the following resources:
  • The topic "COM Custom Resolvers" in SQL Server 2000 Books Online.
  • The chapter "Creating Merge Replication Custom Conflict Resolvers Using Visual Basic" in the SQL Server 2000 Resource Kit.
  • The Microsoft Visual C++ code for a sample provider included on the SQL Server 2000 CD in the \DEVTOOLS\SAMPLES\SQLREPL\RESOLVER\SUBSPRES directory.
Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbprb KB291263
©2003 Microsoft Corporation. All rights reserved.