Custom Conflict Resolver - Not doing anything with a conflict? RRS feed

  • Question

  • We have one specific requirement for an application that if there is a conflict between the publisher and subscriber, we want the users to manually resolve it themselves.  I've looked into the Windows Synchronization Manager and that does not meet our requirements.  As a result, we're going to roll our own conflict resolving interface custom to our application. 

    The SQL Server 2005 replication meets all of our needs except for the custom conflict resolution.  I'm trying to write a custom resolver (using the Microsoft.Samples.SqlServer.BusinessLogicHandler.  I've overridden the UpdateConflictsHandler method, but I don't see a way to ignore conflicts via the ActionOnUpdateConflict enumeration; all the choices are to accept either the custom, default, publisher, or subscriber data. 

    Is there a way to ignore conflicts via a custom resolver?  If not, is there any suggestion on how to do something like this?




    Thursday, July 22, 2010 4:32 PM


  • Unfortunately no. A conflict is logged the resolver is invoked and your code will fire. If you accept custom you might be able to resolve it with publisher data if your SourceIdentifier.SourceIsSubscriber=true, or Subsciber data is SourceIdentifier.SourceIsPublisher=true.


    Perhaps by partitioning to avoid conflicts you can get the behavior you desire.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
    • Proposed as answer by Tom Li - MSFT Tuesday, July 27, 2010 6:11 AM
    • Marked as answer by Tom Li - MSFT Sunday, August 1, 2010 8:37 AM
    Thursday, July 22, 2010 6:51 PM