Microsoft KB Archive/944677

= 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 =

Article ID: 944677

Article Last Modified on 12/11/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

-



Bug: #50001986 (SQL Hotfix)



Notice
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SUMMARY
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



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



CAUSE
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 now 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 Microsoft SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 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 x64-based version


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbsql2005repl kbexpertiseadvanced kbfix kbpubtypekc kbqfe kbhotfixserver KB944677

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.