Article ID: 290917 - View products that this article applies to.
This article was previously published under Q290917
BUG #: 351634 (SHILOH_bugs)
BUG #: 351180 (SHILOH_BUGS)
Inserts into a table may fail due to a "duplicate key values" message when all of the following are true:
The failed CREATE INDEX statement resets the value for the IDENTITY column to its initial seed value.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
The following code reproduces the problem:
The results show that the identity value was incorrectly reinitialized to its seed value.
Server: Msg 1505, Level 16, State 1, Line 1 CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is 'NoIndex1 '. The statement has been terminated. Checking identity information: current identity value '101', current column value '103'. DBCC execution completed. If DBCC printed error messages, contact your system administrator. c1 id ------------------------------ ----------- NoIndex1 100 NoIndex1 101 NoIndex2 102 NoIndex3 103 AfterFailedIndex1 100 AfterFailedIndex2 101 AfterCheckIdent1 104
Contact us for more help
Connect with Answer Desk for expert help.