FIX: Cursor Using Stored Proc After LOAD DB May Get 225 Error

Last reviewed: May 2, 1997
Article ID: Q140871

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 12136 (6.00)

SYMPTOMS

Opening a server-side cursor where the SELECT statement is a stored procedure may result in error 225:

   Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped
   during query optimization

after you load the database with LOAD DATABASE.

CAUSE

If the stored procedure has not already been executed by itself prior to being used in the cursor, the re-resolution of the stored procedure leads to this error.

WORKAROUND

Execute the stored procedure outside the cursor prior to using it with a cursor after a LOAD DATABASE has taken place.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 2 for SQL Server version 6.0. For more information, contact your primary support provider.


Additional query words: sql6 cursor dbcursoropen load database
Keywords : kbbug6.00 kbfix6.00.sp2 kbprg SSrvProg SSrvStProc
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg


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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.