BUG: SQL Admin Not Printing Number of Rows Affected

Last reviewed: April 28, 1997
Article ID: Q89936

The information in this article applies to:

Microsoft SQL Server version 4.2 for OS/2

BUG# OS/2: 7374 (4.2)

SYMPTOMS

When a stored procedure contains multiple SELECT statements, the number of rows affected by the last SELECT statement is not printed. For example, create a stored procedure called "test" as follows:

   create procedure test as
   select * from sysdatabases where 1=2
   select * from sysdatabases where 1=2

Execute test in a query window by typing:

   test

The output produced is:

   (0 rows affected)

This corresponds to the first SELECT statement. The same message, which must appear for the second SELECT statement, is not printed.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here as it becomes available.

Additional query words: stored procedures
Keywords : kbbug4.20 kbtool SSrvSQL_Admin
Version : 4.2
Platform : OS/2

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