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
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.
On This Page
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
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:
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')
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, 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:
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. To create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" section and the online request forms display 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.
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:
822499 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.