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

This article was previously published under Q275624
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57828 (SQLBUG_70)
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 1Violation of PRIMARY KEY constraint 'PK__t1__77BFCB91'.
    Cannot insert duplicate key in object 't1'.
    The statement has been terminated.
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.

Article ID: 275624 - Last Review: 11/02/2013 00:44:00 - Revision: 3.0

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB275624