INF: Enhancement to Trace Flag 1140

Last reviewed: December 19, 1997
Article ID: Q174085

The information in this article applies to:

Microsoft SQL Server, version 6.5

SUMMARY

Trace flag 1140 was originally designed to eliminate the extent-chain scan when attempting to allocate a page to an existing table. One of the most significant side effects of this trace flag was that space in partially- filled extents never got reclaimed; the size of database can grow rapidly where most of the pages in each extent remains unused.

MORE INFORMATION

The enhancement is to limit the extent-chain scan, based on how densely- filled the extents for a table are (density=indused/indreserved). If density >= 90 percent, then stop the extent-chain scan after 'n' allocation pages are searched, where 'n' is (100-density) < 2 (that is, it varies from 1 to 40 as density varies from 90 to 100).

Additional query words:
Keywords : SSrvGen kbusage
Version : WINDOWS:6.50
Platform : winnt
Issue type : kbinfo

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