Knowledge Base

FIX: Correlated Subquery and ISNULL May Cause Disconnect from Server

Article ID: 194666

Article Last Modified on 3/14/2006

Microsoft SQL Server 6.5 Standard Edition

This article was previously published under Q194666

BUG #: 17765 (SQLBUG_65)

SYMPTOMS

A query containing a subquery, which itself contains a correlated subquery using ISNULL, may cause the process connected to SQL Server to disconnect. Under most situations a handled access violation (AV) stack trace will be recorded in the SQL Server error log concurrent with this event.

WORKAROUND

Many subqueries can be flattened to use a join, which would avoid the problem. Additionally, ISNULL can be moved to a prior query so that it can be removed from the correlated subquery.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

Additional query words: sp sp5prodsql av exception subquery ISNULL

Keywords: kbbug kbfix kbsqlserv650sp5fix KB194666