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.
On This Page
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
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:
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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 Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
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. To create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" section and the online request forms display 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.
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 (http://support.microsoft.com/kb/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.
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 (http://support.microsoft.com/kb/308737/)
How to identify the cause of recompilation in an SP:Recompile event
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 = N''col2''))'
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
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 (http://support.microsoft.com/kb/822499/)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Back to the top
