BUG: You receive an "EXCEPTION_ACCESS_VIOLATION" error message when you use a RIGHT OUTER JOIN clause in SQL Server 2000
This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 363638 (SQL Server 8.0)
In Microsoft SQL Server 2000, when you run a query that contains a
RIGHT OUTER JOIN
clause, you may receive an error message that is similar to the following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. Connection Broken Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest SQL Server 2000 service pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4. Steps to reproduce the problem
To reproduce this problem, run the following query in SQL Query Analyzer:
USE pubsgoSELECT *FROM titles tRIGHT OUTER JOIN publishersON publishers.pub_id=t.pub_idAND t.ytd_sales = ( SELECT max(ytd_sales) FROM titles WHERE publishers.pub_id=titles.pub_id)go
After you run this query, you receive the error message and the SQL Server connection is broken.
Article ID: 892451 - Last Review: 12/09/2015 02:03:41 - Revision: 2.4
Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition, Microsoft SQL Server 2000 Workgroup Edition, Microsoft SQL Server 2000 Desktop Engine (Windows), Microsoft SQL Server 2000 Enterprise Edition 64-bit
Keywords: kbnosurvey kbarchive kbbug kbtshoot kbfix KB892451