Microsoft KB Archive/928539

= FIX: An access violation is logged in the SQL Server Errorlog file when you run a query that uses a plan guide in SQL Server 2005 =

Article ID: 928539

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug #: 50000452 (SQL Hotfix)



Notice
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you run a query that uses a plan guide in SQL Server 2005, the query may intermittently fail. Additionally, an access violation that resembles the following is logged in the SQL Server Errorlog file:

2006-08-23 13:34:10.48 spid438 ***Stack Dump being sent to H:\MSSQL\LOG\SQLDump0016.txt

2006-08-23 13:34:10.48 spid438 SqlDumpExceptionHandler: Process 438 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

2006-08-23 13:34:10.48 spid438 * *******************************************************************************

2006-08-23 13:34:10.48 spid438 *

2006-08-23 13:34:10.48 spid438 * BEGIN STACK DUMP:

2006-08-23 13:34:10.48 spid438 * 08/23/06 13:34:10 spid 438

2006-08-23 13:34:10.48 spid438 *

2006-08-23 13:34:10.48 spid438 *

2006-08-23 13:34:10.48 spid438 * Exception Address = 00000000034CE1D0 Module(sqlservr+00000000024CE1D0)

2006-08-23 13:34:10.48 spid438 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION

2006-08-23 13:34:10.48 spid438 * Access Violation occurred reading address 0000000000000010

This problem occurs if the following conditions are true:
 * The query uses a plan guide.
 * The query accepts some parameters.
 * The plan guide applies the OPTIMIZE FOR hint for the query.
 * The query is recompiled before you run the query.



RESOLUTION
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must be running SQL Server 2005 Service Pack 1 (SP1) to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 Itanium architecture version


WORKAROUND
To work around this problem, try to avoid the query recompilation. To determine the reason for the recompilation, use the method that is described in Microsoft Knowledge Base article 308737. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

308737 How to identify the cause of recompilation in an SP:Recompile event



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce the problem
 Open SQL Server Management Studio. Connect to an instance of SQL Server 2005.  Create a new query, and then run the following statements. use tempdb go

create table mytab1 (col1 nvarchar(50), col2 nvarchar(100), col3 int) go

create table mytab2 (a int) go

insert into mytab1 values ('col1 value', 'col2 value', 1) go

insert into mytab2 values (1) go

set quoted_identifier off; go

sp_create_plan_guide N'myplanguide', N'select * from mytab1 join mytab2 on col3 = a where col1 = @p1', N'SQL', NULL, N'@p1 nvarchar(30)', N'OPTION (FAST 40, OPTIMIZE FOR (@p1 = Ncol2))' go

select * from sys.plan_guides go

sp_executesql N'select * from mytab1 join mytab2 on col3 = a where col1 = @p1', N'@p1 nvarchar(30)', N'col2' go

drop table mytab1 go

create table mytab1 (col1 nvarchar(50), col2 nvarchar(100), col3 int) go

sp_executesql N'select * from mytab1 join mytab2 on col3 = a where col1 = @p1', N'@p1 nvarchar(30)', N'col2' go

sp_control_plan_guide N'drop all' go 

<div class="references_section">