FIX: Exception Access Violation Encountered During Query Normalization (281769)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q281769
BUG #: 350968 (SQLBUG_80) BUG #: 350800 (SQLBUG_80)

SYMPTOMS

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 bytes
COpArg::DeriveNormalizedGroupProperties(CTreeHandle * 0x26d1ac28) line 1250 + 8 bytes
COptExpr::DeriveGroupProperties(unsigned long 0) line 2714 + 25 bytes
CImpRuleBaseJoinToIdxLookup::BuildSubstitutes(COptExpr * 0x1c933b2c, CRuleContext * 0x26d1b590, CRuleReturn * 0x26d1b5fc) line 1428
CTask_ApplyRule::Perform(int 5799) line 1692 + 46 bytes
CMemo::ExecuteTasks(COptTask * 0x1c90b3ac, int 0, int 0) line 3453 + 20 bytes
CMemo::OptimizeQuery(CQuery * 0x1c6da8bc, COptExpr * 0x1c8ca63c, double * 0x1c6d430c, int 0, int 0, s_OptimPlans * 0x26d1baf4) line 3779
COptContext::PexprSearchPlan(COptExpr * 0x1c8ca63c) line 1809 + 227 bytes
COptContext::PcxteOptimizeQuery(COptExpr * 0x1c8ca63c, DRgCId * 0x26d1df24) line 1337 + 15 bytes
CQuery::Optimize() line 576 + 16 bytes
CQuery::Optimize(unsigned long 1) line 1101
CCvtTree::PqryFromTree(TREE * 0x1c740c9c, IMemObj * 0x1c6da030, CRangeCollection * 0x1c6da85c, unsigned long 0, CCompPlan * 0x1c6da2bc {CCompPlan}) line 1056 + 25 bytes
BuildQueryFromTree(TREE * 0x1c740c9c, IMemObj * 0x1c6da030, IMemObj * 0x1c6e0020, IQueryObj * * 0x1c6da800, CRangeCollection * 0x1c6da85c, unsigned long 0, CCompPlan * 0x1c6da2bc {CCompPlan}) line 521 + 31 bytes
				

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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.

STATUS

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
				

Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbBug kbfix kbQFE KB281769