INF: Incorrect dpages Error When Creating an Index

Last reviewed: April 28, 1997
Article ID: Q101348

The information in this article applies to:

  - Microsoft SQL Server version 4.2 for OS/2
  - Microsoft SQL Server version 4.2

SUMMARY

When creating an index, you might receive the following message (error number 1520):

   Sort failed because dpages in the sysindexes row for table '%.*s' in
   database '%.*s' had an incorrect value. Please run DBCC CHECKTABLE on
   this table to find the correct value, then contact Technical Support.

MORE INFORMATION

The CREATE INDEX command allocates a work area based on the number of data pages (sysindexes.dpages) in the table. If this value is too low, the work area is too small and the sort fails. SQL Server versions 1.x did not automatically correct the dpages count when a DBCC CHECKTABLE or DBCC CHECKDB was run, so the message directed the user to contact Technical Support to help correct the dpages value.

The DBCC CHECKTABLE and CHECKDB commands in version 4.2 of SQL Server updates the dpages entry to the proper value when they are run. If running DBCC CHECKTABLE corrects the dpages count and reports no other errors, then there's no need to contact your support provider.


Additional query words: Transact-SQL create clustered index Windows NT
Keywords : kbother SSrvServer SSrvWinNT
Version : 4.2 | 4.2
Platform : OS/2 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: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.