FIX: Complex Merge Join Might Cause Handled Access Violation

Article translations Article translations
Article ID: 266158 - View products that this article applies to.
This article was previously published under Q266158
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58007 (SQLBUG_70), 58032 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

Complex merge join queries might cause handled access violations, which terminate the client connection that submitted the query. Because the problem occurs during compilation, it is difficult to determine whether a merge join was the problem. However, by investigating the stack trace reported in the errorlog, this determination is possible if it includes the string "CQScanMergeJoin" in the top most function.

WORKAROUND

Modify the query so that a merge join is not used. One possibility is to use query hints, which are defined in the SQL Server Books Online topic, "Hints".

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 266158 - Last Review: October 20, 2013 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbqfe KB266158

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com