BUG: Using Subquery on MIPS Can Cause Thread Level AV

 Last reviewed: May 2, 1997
Article ID: Q150187

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 14444 (6.00)

SYMPTOMS

If you use a subquery on SQL Server 6.0 running on a MIPS computer, it can cause a thread level access violation (AV).

CAUSE

The following criteria must be present for the problem to occur:

  1. Two levels of subquery, three tables involved.
2. One of the tables must have a unique index. 3. Columns involved in the join must be char/varchar; using int avoids the 
   problem.
4. The amount of data in these tables is critical.

WORKAROUND

Use a join to replace the inner subquery, such as the following, where t is table, c is column:

select my_result= 

   (select count(*) from t2,t3 where t2.c1=t1.c1 and t2.c1=t3.c1)
from t1

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug6.00 kbprg SSrvProg
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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