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

Back to the top

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.

Back to the top

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.

File name	File version	File size	Date	Time	Platform
Spupdsvc.exe	6.2.29.0	22,752	19-Apr-2007	23:45	x86
80sp4-tools.sql	Not applicable	134,628	18-Feb-2006	09:40	Not applicable
Distmdl.ldf	Not applicable	786,432	20-Apr-2007	02:13	Not applicable
Distmdl.mdf	Not applicable	2,359,296	20-Apr-2007	02:13	Not applicable
Dtsui.dll	2000.80.2248.0	1,593,344	20-Apr-2007	05:45	x86
Impprov.dll	2000.80.2248.0	102,400	20-Apr-2007	05:45	x86
Instdist.sql	Not applicable	751,633	28-Nov-2006	23:42	Not applicable
Inst_repl_hotfix.sql	Not applicable	36	28-Feb-2007	02:03	Not applicable
Msgprox.dll	2000.80.2248.0	94,208	20-Apr-2007	05:45	x86
Msrpjt40.dll	4.10.9424.0	188,473	20-Apr-2007	05:45	x86
Mssdi98.dll	8.11.50523.0	239,104	20-Apr-2007	05:45	x86
Ntwdblib.dll	2000.80.2248.0	290,816	20-Apr-2007	05:45	x86
Odsole70.dll	2000.80.2248.0	69,632	20-Apr-2007	05:45	x86
Osql.exe	2000.80.2248.0	57,344	20-Apr-2007	05:45	x86
Pfclnt80.dll	2000.80.2248.0	430,080	20-Apr-2007	05:45	x86
Procsyst.sql	Not applicable	552,068	16-Jun-2005	08:15	Not applicable
Qrdrsvc.exe	2000.80.2248.0	192,512	20-Apr-2007	05:45	x86
Replcom.sql	Not applicable	1,216,659	18-Apr-2007	23:55	Not applicable
Replcom_baseline.sql	Not applicable	1,214,942	08-Dec-2006	10:08	Not applicable
Replmerg.exe	2000.80.2248.0	163,840	20-Apr-2007	05:45	x86
Replmerg.sql	Not applicable	1,151,521	18-Apr-2007	23:55	Not applicable
Replmerg_baseline.sql	Not applicable	1,151,758	28-Feb-2007	02:03	Not applicable
Replprov.dll	2000.80.2248.0	237,568	20-Apr-2007	05:45	x86
Replrec.dll	2000.80.2248.0	315,392	20-Apr-2007	05:45	x86
Replsub.dll	2000.80.2248.0	270,336	20-Apr-2007	05:45	x86
Replsys.sql	Not applicable	1,096,990	08-Dec-2006	10:03	Not applicable
Replsys_baseline.sql	Not applicable	1,096,457	08-Dec-2006	10:08	Not applicable
Repltran.sql	Not applicable	1,000,691	28-Nov-2006	23:42	Not applicable
Repltran_baseline.sql	Not applicable	999,413	08-Dec-2006	10:08	Not applicable
Rinitcom.dll	2000.80.2248.0	278,528	20-Apr-2007	05:45	x86
Semexec.dll	2000.80.2248.0	856,064	20-Apr-2007	05:45	x86
Semmap.dll	2000.80.2248.0	53,248	20-Apr-2007	05:45	x86
Snapshot.exe	2000.80.2248.0	61,440	20-Apr-2007	05:45	x86
Sp4_serv_qfe.sql	Not applicable	18,810	16-Jun-2005	08:15	Not applicable
Sqlagent.exe	2000.80.2248.0	323,584	20-Apr-2007	05:45	x86
Sqldiag.exe	2000.80.2248.0	118,784	20-Apr-2007	05:45	x86
Sqldmo.dll	2000.80.2248.0	4,362,240	20-Apr-2007	05:45	x86
Sqldumper.exe	Not applicable	22,528	20-Apr-2007	05:45	x86
Sqlevn70.rll	2000.80.2248.0	45,056	20-Apr-2007	02:28	Not applicable
Sqlfth75.dll	2000.80.2248.0	102,400	20-Apr-2007	05:45	x86
Sqlservr.exe	2000.80.2248.0	9,175,040	20-Apr-2007	05:46	x86
Sqlsort.dll	2000.80.2248.0	589,824	20-Apr-2007	05:46	x86
Sqlvdi.dll	2000.85.2101.0	122,368	20-Apr-2007	05:45	x86
Stardds.dll	2000.80.2248.0	176,128	20-Apr-2007	05:45	x86
Svrnetcn.dll	2000.80.2248.0	110,592	20-Apr-2007	05:45	x86
Ums.dll	2000.80.2248.0	35,840	20-Apr-2007	05:46	x86
Xpstar.dll	2000.80.2248.0	311,296	20-Apr-2007	05:46	x86
Osql.exe	2000.80.2039.0	57,344	20-Apr-2007	05:47	x86
Sqlse.rll	1.1.2054.0	45,056	19-Apr-2007	23:43	Not applicable
Sqlstpcustomdll.dll	1.1.2054.0	1,846,784	20-Apr-2007	05:47	x86
Sqlstpcustomdll.rll	1.1.2054.0	12,288	19-Apr-2007	23:43	Not applicable
Updspapi.dll	6.2.29.0	371,424	19-Apr-2007	23:45	x86

Back to the top

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

Back to the top

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:

Back to the top