Knowledge Base

FIX: Identity Value Recovery May Fail After a Nonlogged Bulk Load

Article ID: 275624

Article Last Modified on 3/14/2006

APPLIES TO

Microsoft SQL Server 7.0 Standard Edition

This article was previously published under Q275624

BUG #: 57828 (SQLBUG_70)

SYMPTOMS

If SQL Server stops after a nonlogged bulk load operation (BCP and BULK INSERT) into a table with an IDENTITY column, the IDENTITY value may not be properly recovered.

This problem can manifest in the following ways:

As a discrepancy when you run the DBCC CHECKIDENT command:

Checking identity information: current identity value '5', current column value '200'.
As a duplicate entry when you try to insert data into the table:

Server: Msg 2627, Level 14, State 1, Line 1 Violation of PRIMARY KEY constraint 'PK__t1__77BFCB91'.
Cannot insert duplicate key in object 't1'.
The statement has been terminated.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Keywords: kbbug kbfix KB275624

Microsoft KB Archive/275624

FIX: Identity Value Recovery May Fail After a Nonlogged Bulk Load

SYMPTOMS

STATUS