INF: New NO_INDEX Option for SQL Server for Windows NT

Last reviewed: August 13, 1997
Article ID: Q104446

The information in this article applies to:

  - Microsoft SQL Server, version 4.2

SUMMARY

This article provides information on the new NO_INDEX option for DBCC CHECKDB, DBCC CHECKTABLE, and DBCC CHECKALLOC. This enhancement has been added in Microsoft SQL Server version 4.2 for Microsoft Windows NT.

MORE INFORMATION

The syntax for the NO_INDEX option is as follows:

   DBCC CHECKDB (database_name, NO_INDEX)

   DBCC CHECKTABLE (table_name, NO_INDEX)

   DBCC CHECKALLOC (database_name, NO_INDEX)

When the NO_INDEX option is used, only the data portion of user-defined tables is checked for consistency. Indexes are ignored. System tables, however, continue to be checked in their entirety.

Using this option can lead to a substantial reduction in the time that it takes to run the DBCC commands against very large databases. In some cases this time can be so prohibitive as to prevent these consistency checks being run on a regular basis.

In a production environment, the NO_INDEX option is provided to counter such situations. Not checking indexes is relatively safe since problems in index structures can usually be corrected by dropping and recreating the index.

If this option is used, it is still highly recommended that a full CHECKDB and CHECKALLOC be run, whenever possible, to detect any problems in the index structures.


Additional query words: Windows NT
Keywords : SSrvWinNT kbother
Version : 4.2
Platform : WINDOWS
Issue type : kbtshoot


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