Microsoft KB Archive/938825

= FIX: A foreign key constraint that you drop on a table at the publisher is not dropped on the table at the subscriber in a SQL Server 2005 merge replication =

Article ID: 938825

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Express Edition
 * Microsoft SQL Server 2005 Express Edition with Advanced Services
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



BUG #: 50001169 (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 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
In a Microsoft SQL Server 2005 merge replication, you drop a foreign key constraint on a table at the publisher. After you synchronize the data between the publisher and the subscriber, the replication merge agent does not drop the foreign key constraint on the table at the subscriber.

This problem occurs when the related tables at the publisher and at the subscriber do not belong to the dbo schema.



CAUSE
This problem occurs because the replication merge agent runs an incorrect query at the subscriber. When the replication merge agent runs the query, the OBJECT_ID function returns NULL. Then, the IF EXISTS statement returns FALSE. Therefore, the replication merge agent does not run the DROP CONSTRAINT statement.

The following is an example of the query that the replication merge agent runs at the subscriber: IF EXISTS (SELECT * from sysconstraints WHERE constid = OBJECT_ID (N'[FK_DETAIL_TO_MASTER]')) IF OBJECT_ID (N'[Test].[Detail]') IS NOT NULL EXEC ('ALTER TABLE [Test].[Detail] DROP CONSTRAINT FK_DETAIL_TO_MASTER')



Update information
This hotfix is included in cumulative update package 2 (build 3175) for SQL Server 2005 Service Pack 2 (SP2).

To resolve the problem that is described in this article, follow these steps:
 * 1) Install SQL Server 2005 SP2.
 * 2) Install cumulative update package 2 (build 3175) for SQL Server 2005 SP2.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available

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 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
You must have SQL Server 2005 SP2 installed to apply this hotfix.

Restart information
You do not have to restart the computer.

Hotfix replacement information
This hotfix is not replaced by 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 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


WORKAROUND
To work around this problem, manually drop the foreign key constraint on the table at the subscriber.



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



Steps to reproduce the problem

 * 1) Create two tables by using a schema that is not a dbo schema.
 * 2) Create a foreign key constraint on a table to reference a column in another table.

Note When you create the foreign key constraint, the foreign key constraint is created by using a schema that is not a dbo schema.
 * 1) Publish both tables.

Note When you publish the tables, make sure that you perform the following operations:
 * 1) * Specify that the primary key constraint and the foreign key constraint are to be copied to the subscribers.
 * 2) * Specify that the Destination object owner property of the articles is to be an owner other than the dbo user.
 * 3) Initialize a subscription.
 * 4) Drop the foreign key constraint on the publisher.
 * 5) Run the merge agent to synchronize the data between the publisher and the subscriber.

