FIX: Problems with Server Cursors on a Stored ProcedureID: Q175126
|
Running 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:
To work around this problem, do any of the following:
Microsoft 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/.
For more information, contact your primary support provider.
To 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."
Additional query words: responsive spinlock rdo keyset work table
Keywords : kbusage SSrvGPF kbbug6.50 kbfix6.50.SP5
Version : winnt:6.5
Platform : winnt
Issue type : kbbug
Last Reviewed: April 21, 1999