Microsoft KB Archive/913494

= FIX: The merge agent does not use a specified custom user update to handle conflicting UPDATE statements in SQL Server 2005 =

Article ID: 913494

Article Last Modified on 11/4/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 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug #: 74 (SQL Hotfix)



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 this hotfix package
 * The prerequisites for applying the hotfix package
 * Whether you must restart the computer after you apply 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 implement a business logic handler to handle conflicting UPDATE statements during the merge replication synchronization process in Microsoft SQL Server 2005. When you implement the business logic handler, you specify that the business logic handler should use custom user data to resolve a conflict.

In this scenario, when conflicting UPDATE statements occur at both a publisher and a subscriber, the merge agent does not use custom user data to resolve the conflict. Instead, the merge agent uses the updated data at the subscriber to resolve the conflict. Additionally, no conflict row is written to the conflict tables.

This problem occurs when the custom user data is the same as the updated data at the publisher. For example, the publisher contains the following updated data:
 * &quot;Pub1&quot;
 * &quot;Pub2&quot;

The subscriber contains the following updated data:
 * &quot;Sub1&quot;
 * &quot;Sub2&quot;

When you implement the business logic handler, you specify that the business logic handler should use the following custom user data to resolve a conflict:
 * &quot;Pub1&quot;
 * &quot;Custom&quot;

After you perform a merge replication synchronization between the publisher and the subscriber, you notice that the publisher and the subscriber contain the following resolved data:
 * &quot;Sub1&quot;
 * &quot;Custom&quot;

However, you expect the publisher and the subscriber to contain the following resolved data:
 * &quot;Pub1&quot;
 * &quot;Custom&quot;



RESOLUTION
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 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
No prerequisites are required.

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

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Registry information
You do not have to change the registry.

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 Itanium architecture 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
For more information about how to implement a business logic handler, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/ms147911.aspx

For more information about the naming schema for Microsoft 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 kbhotfixserver kbfix kbexpertiseadvanced kbqfe kbpubtypekc KB913494

-

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

© Microsoft Corporation. All rights reserved.