The information in this article applies to:
BUG #: 17338 (6.5) SYMPTOMSRunning a server cursor on a stored procedure may cause SQL Server to stop responding to all clients if all of the following conditions are true:
WORKAROUNDTo work around this problem, do any of the following:
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 INFORMATIONTo determine the type of cursor being used, see the following article in the Microsoft Knowledge Base: Q156489 INF: Overview of SQL Server, ODBC, and DB-Library CursorsTo determine if your query uses a worktable, see the "Worktable n" topic in SQL Server Books Online. You can find this topic in the Administrator's Companion 6.0 under Part 8, "Troubleshooting" in Chapter 23, "Understanding SHOWPLAN Output." Additionally, running sp_recompile is not necessary, but instead a change to the schema_ver column of the sysobjects system table can cause this problem. The following system stored procedures also modify the schema_ver column: sp_bindefault, sp_bindrule, sp_rename, sp_unbindefault, and sp_unbindrule. Additional query words: responsive spinlock rdo keyset work table
Keywords : kbusage SSrvGPF kbbug6.50 kbfix6.50.SP5 |
Last Reviewed: November 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |