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

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

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.

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:

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:

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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, 32-bit version

SQL Server 2005, x64-based version

SQL Server 2005, Itanium architecture version

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

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: