FIX: AV Error Using Temp Table and Cursor in Stored Procedure

 Last reviewed: April 9, 1997
Article ID: Q153987
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

A stored procedure that performs selects against a cursor with a temporary table in the cursor will fail with an access violation or with the following error message: 

   Msg 208 "Invalidobject name #temptable"
The problem will only occur after SQL Server has been shut down and restarted after the initial creation of the stored procedure. If the stored procedure is then dropped and re-created, it will work again until SQL Server is shut down and restarted.

CAUSE

On recompile of the stored procedure, the temporary tables are not being resolved properly if they are being invoked from inside a cursor.

WORKAROUND

The problem only occurs if both the temporary table and the cursor are both created inside a stored procedure. Creating the temporary table outside of the stored procedure will allow the stored procedure to function correctly. An alternative workaround would be to convert the temporary table to a permanent table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Additional query words:
Keywords : kbbug6.50 kbfix6.50.sp1 kbnetwork SSrvStProc
Version : 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.