Microsoft KB Archive/87483

{|
 * width="100%"|

The information in this article applies to:
 * Microsoft SQL Server, version 4.2 for OS/2

BUG# OS/2: 7294 (4.20)

SYMPTOMS
In SAF and the SQL Administrator, if a batch query contains errors, the result windows do not display the entire result set. Instead, the result set is incomplete, even though the batch is not aborted.

To see this behavior, first create a table with a unique index:

create table t (c int) create unique clustered index tind on t (c) insert t values(0) go Then run the following query that causes multiple errors: insert t values(0)      /* insert duplicate key */ insert t values(1) select 1 insert t values(0)      /* insert duplicate key */ insert t values(2) select 2 insert t values(0)      /* insert duplicate key */ insert t values(3) select 3

CAUSE
In SAF, the result window displays only the result of the SQL statements after the first error and before the second error. In the sample query, only &quot;1&quot; appears in the result window, along with two error messages about trying to insert a duplicate key. The rest of the result seems to remain in the buffer. If you execute the same query again, and the batch has more than two errors (as in the sample query), the following error occurs:

SQL Server Error (Severity 7 errorno 10038 os-1) Continue SAF? Attempt to initiate a new SQL Server operation with result pending. In SQL Administrator, SQL Server behaves a little differently because the errors appear in dialog boxes. Whether the result of a SQL statement appears or not depends on where the statement is and how many errors occur in the batch. In the sample query, only &quot;2&quot; appears in the result window. SQL Administrator ignores both &quot;1&quot; and &quot;3,&quot; though all INSERT statements other than &quot;insert t values(0)&quot; run correctly. No such behaviors occur in ISQL.

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 in the Microsoft Knowledge Base as it becomes available.

NOTE: This problem also occurs in SAF versions 1.1x.
 * }

-

Last reviewed: April 28, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.