The information in this article applies to:
BUG #: 17490 SYMPTOMS
Executing a DELETE statement against a table that has an index defined
using a FILLFACTOR of 100 percent may cause the connection or the entire
server to stop responding.
CAUSE
The connection is caught in an infinite loop. WORKAROUNDTo work around this problem, allow some free space on your index pages by specifying a FILLFACTOR of less than 100 percent (such as using FILLFACTOR=80). In addition to avoiding exposure to the above problem, doing this allows SQL Server to process your DELETE statement more efficiently. STATUSMicrosoft has confirmed this to be a problem in SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 5a
for Microsoft SQL Server version 6.5. For information about
downloading and installing the latest SQL Server Service Pack, see
http://support.microsoft.com/support/sql/.
MORE INFORMATION
The type of index involved makes no difference to this problem. That is, it
can happen with clustered, non-clustered, unique, and non-unique indexes.
Additional query words: create hang hung freeze frozen lock locked up
Keywords : kbusage SSrvGen kbbug6.50 kbfix6.50.SP5 |
Last Reviewed: November 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |