Microsoft KB Archive/324515

= FIX: Update Conflict for Unique Key Columns for Queued Updating Subscriber Results in Non-Convergence =

Article ID: 324515

Article Last Modified on 9/27/2005

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q324515



BUG #: 358965 (SHILOH_BUGS)



SYMPTOMS
An update conflict might result in non-convergence under the following circumstances:


 * An article is defined to a transactional publication that supports queued updating subscribers.
 * One or more columns that are defined to a unique index or a unique constraint experiences a unique key update conflict.

If you configure a publication as Publisher wins conflict resolution, the symptoms that occur are:
 * The Distribution Agent deletes the row from the Subscriber that has the same primary key as the conflict winner row and never inserts the Publisher's version of the row at the Subscriber.
 * The Distribution Agent updates the row that has the same primary key as the conflict losing row at the Subscriber so that the row reflects the values of the Publisher's version of the row.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix has the file attributes (or later) 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 tool in Control Panel.   Date          Time      Version     Size           File name -

06-12-2002  21:48:55   8.00.0643   96,966 bytes   Qfe358965.sql NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.



MORE INFORMATION
After you apply this fix, you must drop and then re-create the publication.