BUG: 7.0 ISQL.EXE Returns Different Results than 6.5 ISQL.EXE

ID: Q234890

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 55842 (SQLBUG_70)

SYMPTOMS

Running the following stored procedure created in the pubs database against SQL Server version 7.0:


CREATE PROCEDURE dbo.my_proc
  AS  BEGIN
     SET NOCOUNT ON
     SELECT '000', '1','2','3','4','5','6','7','8','9','0'
     SELECT '010', '1','2','3','4','5','6','7','8','9','0'
     SELECT '020', '1','2','3','4','5','6','7','8','9','0'
  END

using the following command line:


   isql /Usa /P /dpubs /h-1 /s /Q"exec my_proc" /ooutput.txt

returns the following results in the Output.txt file when using Isql.exe from SQL Server version 6.5:


   0001234567890

   0101234567890

   0201234567890

When run using Isql.exe from SQL Server version 7.0, Output.txt contains:


   0001234567890
   010
   1234567890
   020
   1234567890

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

If the results are displayed on the screen instead of being sent to an output file, the 7.0 results match the 6.5 results.

Additional query words:


Keywords          : kbSQLServ700bug 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: June 21, 1999