BUG: SQLExecutive, CmdExec Task Output Is Not Properly Reported

ID: Q197243

The information in this article applies to:

Microsoft SQL Server version 6.5

SYMPTOMS

The SQLExecutive, CmdExec task opens a file and redirects the stdout and stderr to it. When the task is complete SQLExecutive reads through the file in 231 byte increments. If the output is not on a boundary, > 231 bytes, the data is not reported.

For example, 245 bytes causes a second read loop to take place but the bytes read does not equal the requested buffer size of 231 bytes. The task ignores the second read and reports the first 231 bytes instead of the last 231 bytes.

WORKAROUND

To avoid the problem you can attempt to ensure that the output of the task is less than 231 bytes total or that the task output ends on a 231 byte boundary.

STATUS

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

MORE INFORMATION

You can start SQLExecutive from the Windows NT command prompt using the following command

 sqlexec -c ?v

to see the actual output. However, the final output will not be reported in the task history correctly.

Additional query words: prodsql

Keywords          : kbbug6.50 
Version           : WINNT:6.5
Platform          : winnt
Issue type        : kbbug

Last Reviewed: December 30, 1998