FIX: OrigFillFactor Reports Wrong Value for Non-Clustered Index

 Last reviewed: June 27, 1997
Article ID: Q165099
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG#: 16553 (6.5)

SYMPTOMS

OrigFillFactor reports the incorrect value for a non-clustered index once a clustered index is rebuilt with "zero" fillfactor using DBCC DBREINDEX.

Another possible side effect of specifying a zero fillfactor is the intermittent problem of the users of the database in question experiencing error 1105 on the "default" segment, even though there is plenty of space available for this segment within the database. This problem is described more fully in the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q164578
   TITLE     : BUG: Error 1105 on Default Segment When Running DBCC
               DBREINDEX
Shutting down and restarting the server may temporarily clear the symptoms of this problem. However, a shutdown is unnecessary when using the solution described in the WORKAROUND section of this article.

WORKAROUND

To work around this problem, specify a non-zero fillfactor when rebuilding the clustered index.

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 : kbbug6.50 kbfix6.50.sp3 SSrvAdmin SSrvGen
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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.