Microsoft KB Archive/165099: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 49: | Line 49: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
OrigFillFactor reports the incorrect value for a non-clustered index once a clustered index is rebuilt with | OrigFillFactor reports the incorrect value for a non-clustered index once a clustered index is rebuilt with "zero" fillfactor using DBCC DBREINDEX.<br /> | ||
<br /> | <br /> | ||
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 | 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:<br /> | ||
<div class="indent"> | <div class="indent"> |
Latest revision as of 11:02, 21 July 2020
Article ID: 165099
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q165099
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:
164578 : 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: kbbug kbfix KB165099