This article describes the following about this hotfix release:

• The issues that are fixed by the hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

After you restart a computer that is running Microsoft SQL Server 2005, the following problems may occur:

• When SQL Server starts, an application query that reads lots of data as soon as the query connects may be slow.
• The SQL Server service may take a long time to start.

Note These problems do not occur in Microsoft SQL Server 2005 Enterprise Edition, in Microsoft SQL Server 2005 Developer Edition, or in Microsoft SQL Server 2005 Evaluation Edition.

These problems occur because some types of intensive front-end application queries may have long compilation waiting times when SQL Server starts. The long compilation waiting times occur when application metadata is populated in the SQL Server buffer pool.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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, contact 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.

Prerequisites

There are no prerequisites for this hotfix.

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 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 tool in Control Panel.

SQL Server 2005 32-bit versions

SQL Server 2005 64-bit version

SQL Server 2005 Itanium architecture version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.

This hotfix exposes trace flag 840. When trace flag 840 is turned on, SQL Server can perform larger I/O extent reads to populate the buffer pool when SQL Server starts. The larger I/O extent reads populate the buffer pool faster. Additionally, the larger I/O extent reads improve the initial query compilation and the response time when SQL Server starts. For more information about how to turn on trace flag 840, see the "Using the SQL Server service startup options" topic in SQL Server 2005 Books Online.

Note SQL Server 2005 Enterprise Edition, SQL Server 2005 Developer Edition, and SQL Server 2005 Evaluation Edition can already perform 64-KB I/O extent reads during buffer pool ramp-up. Therefore, you do not have to apply this hotfix to SQL Server 2005 Enterprise Edition, to SQL Server 2005 Developer Edition, or to SQL Server 2005 Evaluation Edition.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: