Knowledge Base

BUG: Concurrent Cursors and Stored Procedures Against the Same Table May Cause an Access Violation

Article ID: 178285

Article Last Modified on 10/3/2003

APPLIES TO

This article was previously published under Q178285
BUG #: Windows NT: 17371 (6.5)

SYMPTOMS

Concurrent cursor and stored procedure access to the same table may result in a handled access violation (AV) and possibly cause the server to stop responding. The problem is specific to SQL Server running on a SMP computer.

WORKAROUND

To work around this problem, do either of the following:
  • Reduce the concurrency of cursor and stored procedure access to the same table.

    -or-
  • Increase the amount of memory for the procedure cache.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This problem has only been observed when procedure cache is heavily used and is near its capacity. The client application may receive the following error before the AV:
Msg 701, "There is insufficient system memory to run this query."

Additional query words: hang hung freeze frozen lock locked up crash crashed st proc stproc

Keywords: kbbug kbsqlserv650bug KB178285


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.