FIX: CREATE INDEX Aborts with Error 1509 or 632

 Last reviewed: May 2, 1997
Article ID: Q140265

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 12183 (6.00)

SYMPTOMS

When you attempt to create an index on a table, the command may abort with one of the following two possible errors: 

   Msg 1509, Level 20, State 3:
   Row compare failure

   Error: 632, Severity: 20, State: 1
   Memmove() was called with a length of %d - maximum allowed length is
   2048.
NOTE: This problem only occurs under rare conditions and is not likely to occur with most CREATE INDEX statements.

WORKAROUND

Increase the "sort pages" configuration parameter from the default of 64 to a higher number using the sp_configure system stored procedure. In most cases, increasing this parameter from the default of 64 to 128 will allow the index to be created; however, it can be increased to a maximum of 511 if necessary.

NOTE: Before modifying the number of sort pages, you need to issue the command: 

   sp_configure 'allow updates', 1
along with a corresponding: 

   sp_configure 'allow updates', 0
at the end of the process.

STATUS

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

Additional query words: sql6 windows nt
Keywords : kbbug6.00 kbfix6.00.sp3 kbusage SSrvGen
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.