FIX: The foreign key that you created between two tables does not work after you run the CREATE INDEX statement in SQL Server 2000

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

Consider the following scenario. You create a foreign key between table A and table B in Microsoft SQL Server 2000. You run the CREATE INDEX statement for table A. In this scenario, the following symptoms occur:

• The foreign key that was created between the two tables does not work.
• You can drop the primary key constraint on table A, even if the primary key is referenced by the foreign key constraint on table B.
• If you run the DBCC CHECKCATALOG statement against this database, you receive the following error message:
  Server: Msg 2513, Level 16, State 14, Line 1
  Table error: Object ID ObjectID (object 'ObjectName') does not match between 'SYSREFERENCES' and 'SYSINDEXES'.
  DBCC results for 'current database'.
  DBCC execution completed. If DBCC printed error messages, contact your system administrator.

This problem occurs if the following conditions are true:

• A nonclustered index or a statistic exists on table A.
• A nonclustered primary key is created on table A. The newly created primary key has a larger value of the indid column in the sysindexes system table than the value of the indid column of the index or the statistic that is mentioned in the first item.
• A foreign key exists on table B and references the primary key of table A.
• The nonclustered index or the statistic that is mentioned in the first item is dropped.
• You run the CREATE INDEX statement to create an index on table A.
• In the CREATE INDEX statement, you set the DROP_EXISTING option to ON to drop the existing primary key.

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.

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

To apply this hotfix, you must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed on the computer. For information about how to obtain SQL Server 2000 SP4, see the following article in the Microsoft Knowledge Base:

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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.

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

Steps to reproduce the problem

1. Start SQL Query Analyzer, and then create a new query.
2. Run the following statements.

   create table x( a int not null, b int not null, c int not null) 
   go 
   create clustered index xcidx on x(a) 
   go 
   create statistics xstat on x(c) 
   go 
   alter table x add constraint xpk primary key nonclustered (b) 
   go 
   create table y (b int not null, c int not null) 
   go 
   alter table y add constraint yfk foreign key (b) references x(b) 
   go 
   select * from sysindexes where id = object_id('x') 
   select * from sysreferences where fkeyid = object_id('y') and rkeyid = object_id('x') 
   go 
   drop statistics x.xstat 
   go 
   create clustered index xcidx on x(a) with drop_existing, sort_in_tempdb 
   create unique nonclustered index xpk on x(b) with drop_existing, sort_in_tempdb 
   go 
   print 'sysreferences now out of sync' 
   select * from sysindexes where id = object_id('x') 
   select * from sysreferences where fkeyid = object_id('y') and rkeyid = object_id('x') 
   go 
   dbcc checkcatalog 
   go
   

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: