Article ID: 194662 - View products that this article applies to.
This article was previously published under Q194662
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 17134 (SQLBUG_65)
If multiple connections are simultaneously creating and dropping stored procedures, an error 707 may be generated and SQL Server may appear to stop responding (hang). However, the SQL Server process is actually in a CPU- intensive loop and the system will return to normal within a few minutes.
A typical situation in which this might occur is when an ODBC-based application which is calling SQLPrepare() has also selected the option to create temporary stored procedures. These stored procedures are usually dropped when the connection is closed, but may also be dropped when the ODBC statement handle is closed, if the option is set to SQL_UP_ON_DROP. For additional information about prepared statements, please see the following article in the Microsoft Knowledge Base:
Msg 707: System error detected during attempt to free memory at address 0x1a99000. Please consult the SQL Server error log for more details.
(http://support.microsoft.com/kb/151536/EN-US/ )INF: SQLPrepare and Temporary Stored Procedures in SQL Server
To avoid this problem, minimize the number of times that procedures are created and dropped by either disabling the option to generate temporary stored procedures for prepared statements, or by dropping the procedures only when the connection is closed.
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
197177For more information, contact your primary support provider.
(http://support.microsoft.com/kb/197177/ )INF: How to Obtain SQL Server 6.5 Service Pack 5a
Article ID: 194662 - Last Review: October 10, 2013 - Revision: 4.0