FIX: Cursor Declaration In a Stored Procedure Causes Client AV

Last reviewed: May 1, 1997
Article ID: Q136966

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 11169 (6.00)

SYMPTOMS

Cursor declaration inside a stored procedure with aggregates and a variable can cause a client access violation (AV) during the execution of the stored procedure.

WORKAROUND

Perform an initial SELECT with the entire WHERE clause and INSERT into a temporary table, such as:

   insert <temp storage>  select <cols>
   from <table> where <clauses>

followed by DECLARE CURSOR from the temporary table:

   declare cursor for select col1 = sum(...)
   from <temp storage>

STATUS

Microsoft has confirmed this to be a problem in 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.

MORE INFORMATION

The replication scenario performs a DECLARE CURSOR by SELECTing an aggregate and has a variable referenced in the WHERE clause.

Additional query words: sql6 declare cursor av stproc
Keywords : kbbug6.00 kbfix6.00.sp1 kbprg SSrvProg SSrvStProc
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: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.