Microsoft KB Archive/945897

= FIX: The row at the publisher contains incorrect values in the column that has the UniqueIdentifier data type when you synchronize a subscription in a merge replication between SQL Server 2005 and SQL Server 2005 Compact Edition =

Article ID: 945897

Article Last Modified on 1/7/2008

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition

-



Bug #: 50001924



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.



SYMPTOMS
Consider the following scenario. You create a merge replication between Microsoft SQL Server 2005 and SQL Server 2005 Compact Edition. You insert a row into a table at a subscriber. You synchronize the subscription. In this scenario, the row at the publisher contains incorrect values in the column that has the UniqueIdentifier data type. The value appears in the following format:

00000001-0001-0000-

This problem occurs when the following conditions are true.

Conditions for the table in SQL Server 2005

 * The table contains a computed column or a column that has the Timestamp data type.
 * The table contains a column that has the UniqueIdentifier data type. Additionally, the ROWGUIDCOL property is enabled on this column.

Note This column is already added before you create the merge publication.
 * The column of the UniqueIdentifier data type is not the last column in the table.

Conditions for the merge publication

 * You include the table in the merge publication.
 * In the merge publication, you exclude the computed column or the column that has the Timestamp data type.
 * In the merge publication, the column of the UniqueIdentifier data type is the last column that you include.



RESOLUTION
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



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 what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

