FIX: Error 2610 on Insert into Table with Multiple Indexes

Last reviewed: June 27, 1997
Article ID: Q164576

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 16591

SYMPTOMS

If you use "INSERT INTO <table> SELECT <select statement>" to add rows to a table that has a non-unique clustered index and at least one non- clustered index, you may encounter the following error:

   Msg 2610, Level 22, State 1
   Could not find leaf row in nonclustered index'%.*s' that corresponds to
   data row from logical data page %Id, row offset %d during update index
   attempt after data page split.

After this error occurs, the connection to SQL Server is broken.

WORKAROUND

To work around this problem, do any one of the following:

Make the clustered index unique.
Drop some or all of the non-clustered indexes for the duration of the insert.
Drop the clustered index for the duration of the insert.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Keywords : kbusage SSrvGen kbbug6.5
Version : 6.5
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.