FIX: Coalesce with Subquery May Generate an Access Violation

This article was previously published under Q298803
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 352326 (SHILOH_BUGS)
When you run a coalesce query that contains a subquery the following error message may occur:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
Change the query so that it uses CASE WHEN or IF ELSE statements instead.For example:
  • CASE   WHEN (expression1 IS NOT NULL) THEN expression1   ...   WHEN (expressionN IS NOT NULL) THEN expressionN   ELSE NULL						

  • IF (expression1 IS NOT NULL) expression1   ELSE    IF (expression2 IS NOT NULL) expression2   ...   ELSE NULL						
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
To reproduce the problem, use this code:
USE northwindGOSELECT COALESCE     ((SELECT COUNT(p.productid)      FROM  Products p       INNER JOIN Suppliers s       ON p.supplierid = s.supplierid       WHERE city = 'London' ),0)GO				

Article ID: 298803 - Last Review: 01/16/2015 22:34:54 - Revision: 3.2

  • Microsoft SQL Server 2000 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB298803