FIX: Conflicts are not logged when you use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver for an article in a merge replication in Microsoft SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by the hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario. You configure a merge replication in SQL Server 2005. You add an article to the publication. You specify the article to use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver. When you make some changes to the article on a subscriber, those changes may be undone during later synchronizations. However, you cannot find any conflict in Replication Monitor or in the conflict table.

This issue occurs because the conflict is not logged in Replication Monitor or in the conflict table. SQL Server does not log a conflict when the last change is not made on the publisher. For example, if two subscribers update the same row while they are offline, the first subscriber successfully uploads the change to the publisher. When the second subscriber uploads the change to the publisher, SQL Server detects a conflict. However, SQL Server does not log the conflict because last change is not made on the publisher when you use Microsoft SQL Server Subscriber Always Wins Conflict Resolver.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

• SQL Server 2005 Service Pack 2
  
  For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
  913089  (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 32-bit version

SQL Server 2005 x64-based version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

After you apply this hotfix, conflicts are logged correctly when the Microsoft SQL Server Subscriber Always Wins Conflict Resolver is used and when the last change is not made on the publisher.

Steps to reproduce this issue

1. In SQL Server 2005, create a publication of a merge replication.
2. Add an article to the publication. Specify Microsoft SQL Server Subscriber Always Wins Conflict Resolver for the article.
3. Create two subscribers for the publication. Name the subscribers Sub1 and Sub2.
4. Change some data in a row on Sub1.
5. Synchronize data between the publisher and Sub1.
6. Change some data in the same row on Sub2.
7. Synchronize data between the publisher and Sub2.

When you examine the data on the publisher, you find that the changes that you made on Sub1 are lost. However, the conflict is not logged.

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: