The information in this article applies to:
BUG #: 53836 (SQLBUG_70) SYMPTOMSWhen a table contains a foreign key that references a column other than the first column in the parent table, DBCC CHECKCATALOG may incorrectly report error 2513. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If You Are Eligible for No-Charge Technical Support WORKAROUNDCreate the parent table so that the primary key constraint can be placed on the first column of the table. STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATION
To determine if the error reported is legitimate, manually test the foreign key constraint to see if it is being enforced correctly. For example, try inserting a record into the foreign key table with a value that does not have a corresponding entry in the primary key table. If the insertion fails, then the foreign key constraint is being enforced correctly and the 2513 error message can be ignored. However, if the insertion succeeds, then the foreign key constraint is not being enforced correctly and the 2513 error message is legitimate.
Additional query words:
Keywords : kbSQLServ700bug kbDSupport |
Last Reviewed: December 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |