FIX: Exception Access Violation Encountered During Query Normalization

This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 350968 (SQLBUG_80)BUG #: 350800 (SQLBUG_80)
The SQL Server may encounter an access violation exception during normalization. The following or similar stack track is generated in the SQL Server error log indicating you have encountered the failure condition:
CGroupProperties::FTableGroup() line 52 + 18 bytesCOpArg::DeriveNormalizedGroupProperties(CTreeHandle * 0x26d1ac28) line 1250 + 8 bytesCOptExpr::DeriveGroupProperties(unsigned long 0) line 2714 + 25 bytesCImpRuleBaseJoinToIdxLookup::BuildSubstitutes(COptExpr * 0x1c933b2c, CRuleContext * 0x26d1b590, CRuleReturn * 0x26d1b5fc) line 1428CTask_ApplyRule::Perform(int 5799) line 1692 + 46 bytesCMemo::ExecuteTasks(COptTask * 0x1c90b3ac, int 0, int 0) line 3453 + 20 bytesCMemo::OptimizeQuery(CQuery * 0x1c6da8bc, COptExpr * 0x1c8ca63c, double * 0x1c6d430c, int 0, int 0, s_OptimPlans * 0x26d1baf4) line 3779COptContext::PexprSearchPlan(COptExpr * 0x1c8ca63c) line 1809 + 227 bytesCOptContext::PcxteOptimizeQuery(COptExpr * 0x1c8ca63c, DRgCId * 0x26d1df24) line 1337 + 15 bytesCQuery::Optimize() line 576 + 16 bytesCQuery::Optimize(unsigned long 1) line 1101CCvtTree::PqryFromTree(TREE * 0x1c740c9c, IMemObj * 0x1c6da030, CRangeCollection * 0x1c6da85c, unsigned long 0, CCompPlan * 0x1c6da2bc {CCompPlan}) line 1056 + 25 bytesBuildQueryFromTree(TREE * 0x1c740c9c, IMemObj * 0x1c6da030, IMemObj * 0x1c6e0020, IQueryObj * * 0x1c6da800, CRangeCollection * 0x1c6da85c, unsigned long 0, CCompPlan * 0x1c6da2bc {CCompPlan}) line 521 + 31 bytes				
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
   File name     Platform   ----------------------   s80222i.exe   Intel				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Microsoft has confirmed this to be a problem in SQL Server 2000.
More information
Because the problem is encountered during query normalization, attempts to view the SHOWPLAN of the query lead to the exception condition as well.

An example of a query that leads to the problem condition follows. It generally requires 2 or more tables resulting in a correlation or grouping evaluation as shown.
SELECT DestinationPage.NetworkId FROM DailyTQSContextUsage_20001103,      DestinationPage,      Geography  WHERE   DESTINATIONPAGE.PAGEID =              DAILYTQSCONTEXTUSAGE_20001103.TARGETPAGEID      AND                                Geography.CountryId =             DAILYTQSCONTEXTUSAGE_20001103.COUNTRYID				

Article ID: 281769 - Last Review: 01/16/2015 21:18:21 - Revision: 4.0

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbfix kbqfe KB281769