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 translations Article translations
Article ID: 938825 - View products that this article applies to.
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.
Expand all | Collapse all

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

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')

RESOLUTION

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 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:
http://support.microsoft.com/contactus/?ws=support
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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200715:05x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3175.0296,30414-Jun-200715:05x86
Msmdlocal.dll9.0.3175.015,948,14414-Jun-200715:05x86
Mssqlsystemresource.ldfNot applicable524,28814-Jun-200711:22Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56814-Jun-200711:22Not applicable
Odsole70.dll2005.90.3175.059,24814-Jun-200715:05x86
Rdistcom.dll2005.90.3175.0644,97614-Jun-200715:05x86
Replmerg.exe2005.90.3175.0320,88014-Jun-200715:05x86
Replrec.dll2005.90.3175.0784,75214-Jun-200715:05x86
Sqlaccess.dll2005.90.3175.0350,57614-Jun-200715:05x86
Sqlservr.exe2005.90.3175.029,193,07214-Jun-200715:05x86
Sqlwep.dll2005.90.3175.090,99214-Jun-200715:05x86
Sqsrvres.dll2005.90.3175.070,51214-Jun-200715:05x86
Sysdbupg.sqlNot applicable510,62213-Jun-200720:46Not applicable
Xpstar90.dll2005.90.3175.0295,79214-Jun-200715:05x86
SQL Server 2005, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200714:05x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3175.0296,30414-Jun-200714:05x86
Msmdlocal.dll9.0.3175.015,948,14414-Jun-200714:05x86
Mssqlsystemresource.ldfNot applicable524,28814-Jun-200710:22Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56814-Jun-200710:22Not applicable
Odsole70.dll2005.90.3175.090,48014-Jun-200716:41x64
Rdistcom.dll2005.90.3175.0828,78414-Jun-200716:41x64
Replmerg.exe2005.90.3175.0417,64814-Jun-200716:41x64
Replrec.dll2005.90.3175.01,011,56814-Jun-200716:41x64
Sqlaccess.dll2005.90.3175.0357,74414-Jun-200716:41x86
Sqlservr.exe2005.90.3175.039,674,22414-Jun-200716:41x64
Sqlwep.dll2005.90.3175.090,99214-Jun-200714:05x86
Sqlwep.dll2005.90.3175.0123,76014-Jun-200716:41x64
Sqsrvres.dll2005.90.3175.083,31214-Jun-200716:41x64
Sysdbupg.sqlNot applicable510,62213-Jun-200719:46Not applicable
Xpstar90.dll2005.90.3175.0546,67214-Jun-200716:41x64
SQL Server 2005, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200715:05x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3175.0296,30414-Jun-200715:05x86
Msmdlocal.dll9.0.3175.049,904,49614-Jun-200719:56IA-64
Mssqlsystemresource.ldfNot applicable524,28814-Jun-200711:22Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56814-Jun-200711:22Not applicable
Odsole70.dll2005.90.3175.0179,56814-Jun-200719:56IA-64
Rdistcom.dll2005.90.3175.01,885,55214-Jun-200719:56IA-64
Replmerg.exe2005.90.3175.0957,29614-Jun-200719:56IA-64
Replrec.dll2005.90.3175.02,145,13614-Jun-200719:56IA-64
Sqlaccess.dll2005.90.3175.0352,11214-Jun-200719:56x86
Sqlservr.exe2005.90.3175.072,530,80014-Jun-200719:56IA-64
Sqlwep.dll2005.90.3175.090,99214-Jun-200715:05x86
Sqlwep.dll2005.90.3175.0221,04014-Jun-200719:56IA-64
Sqsrvres.dll2005.90.3175.0147,31214-Jun-200719:56IA-64
Sysdbupg.sqlNot applicable510,62213-Jun-200720:46Not applicable
Xpstar90.dll2005.90.3175.0957,29614-Jun-200719:56IA-64

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 "Applies to" section.

MORE INFORMATION

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.
  3. Publish both tables.

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

REFERENCES

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 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 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 938825 - Last Review: November 20, 2007 - Revision: 1.4
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
Keywords: 
kbautohotfix kbhotfixserver kbexpertiseadvanced kbqfe kbfix KB938825

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com