FIX: Open Cursor Statement in SP Sets Variables to NULL

Last reviewed: April 30, 1997
Article ID: Q135301

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

SYMPTOMS

When you open a cursor in a stored procedure, it can set all local variables inside the stored procedure to NULL if the DECLARE cursor statement is the first statement in the stored procedure.

WORKAROUND

Either of the following methods can be used to work around this problem:

Do not use the DECLARE cursor statement as the first statement in the stored procedure.

-OR-

Issue the DECLARE cursor statement inside an EXECUTE statement as follows:

   EXEC ("DECLARE mycursor cursor for SELECT au_lname from authors")

STATUS

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


Additional query words: sql6
Keywords : kbbug6.00 kbfix6.00.sp1 kbprg SSrvProg SSrvStProc SSrvTran_SQL
Version : 6.0
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 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.