FIX: T-SQL Cursors Ignore NOCOUNT Query Option & Trace Flag 364

 Last reviewed: March 17, 1998
Article ID: Q172549
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 17091 (WINDOWS: 6.5)

SYMPTOMS

When executing a Transact-SQL cursor, the cursor returns empty result sets (DONE_IN_PROC messages) even when NOCOUNT or trace flag 3640 is enabled.

This means that if you do 100 fetch operations into local variables, the client must process 100 empty result sets.

CAUSE

The NOCOUNT and trace flag 3640 settings are ignored by cursor processing.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

MORE INFORMATION

For more information, see the following articles in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q165951
   TITLE     : INF: Result Processing for SQL Server

   ARTICLE-ID: Q151599
   TITLE     : INF: How to Process Results in an ESQL Application

Additional query words: tsql t-sql transql tran-sql
Keywords : kbbug6.00 kbbug6.50 SSrvGen SSrvProg SSrvTran_SQL kbfix6.50.sp4 kbprg kbusage
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

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