FIX: An application query that reads lots of data may be slow, and the SQL Server service may take a long time to start in SQL Server 2005 (912322)


The information in this article applies to:

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup
  • Microsoft SQL Server 2005 Express Edition
Bug #: 20011905 (SQLBUDT)
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.

SUMMARY

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

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

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:

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

Hotfix information

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
File nameFile versionFile sizeDateTimePlatform
Dtspipeline.dll2005.90.1518.0600,28021-Jan-200601:11x86
Msmdlocal.dll9.0.1518.015,585,49621-Jan-200601:11x86
Msmdpp.dll9.0.1518.03,826,39221-Jan-200601:11x86
Msmdpump.dll9.0.1518.03,913,43221-Jan-200601:11x86
Msmdredir.dll9.0.1518.03,927,25621-Jan-200601:11x86
Msmdsrv.exe9.0.1518.014,564,05621-Jan-200601:11x86
Msmgdsrv.dll9.0.1518.05,935,32021-Jan-200601:11x86
Msolap90.dll9.0.1518.04,204,76021-Jan-200601:11x86
Nsservice.exe9.0.1518.018,64821-Jan-200601:10x86
Osql.exe2005.90.1518.051,41621-Jan-200601:11x86
Sqlaccess.dll2005.90.1518.0349,40021-Jan-200601:11x86
Sqlca.dll2005.90.1518.03,207,38421-Jan-200601:11x86
Sqldiscoveryapi_s.dll2005.90.1518.0527,06421-Jan-200601:11x86
Sqlncli.dll2005.90.1518.02,208,52821-Jan-200601:10x86
Sqlservr.exe2005.90.1518.028,778,25621-Jan-200601:11x86
Txbestmatch.dll2005.90.1518.0430,29621-Jan-200601:11x86
SQL Server 2005 64-bit version
File nameFile versionFile sizeDateTimePlatform
Dtspipeline.dll2005.90.1518.01,054,93621-Jan-200605:14x64
Msmdlocal.dll9.0.1518.030,011,60821-Jan-200605:15x64
Msmdpp.dll9.0.1518.04,884,18421-Jan-200605:14x64
Msmdpump.dll9.0.1518.04,957,40021-Jan-200605:14x64
Msmdredir.dll9.0.1518.04,831,96021-Jan-200605:14x64
Msmdsrv.exe9.0.1518.029,336,28021-Jan-200605:15x64
Msmgdsrv.dll9.0.1518.08,909,52821-Jan-200605:14x64
Msolap90.dll9.0.1518.05,667,03221-Jan-200605:14x64
Nsservice.exe9.0.1518.018,64821-Jan-200605:13x86
Osql.exe2005.90.1518.083,67221-Jan-200605:14x64
Sqlaccess.dll2005.90.1518.0356,56821-Jan-200605:14x86
Sqlca.dll2005.90.1518.04,278,48821-Jan-200605:14x64
Sqldiscoveryapi_s.dll2005.90.1518.0745,68821-Jan-200605:14x64
Sqlncli.dll2005.90.1518.03,151,63221-Jan-200605:14x64
Sqlservr.exe2005.90.1518.039,397,59221-Jan-200605:14x64
Txbestmatch.dll2005.90.1518.0872,15221-Jan-200605:14x64
SQL Server 2005 Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Msmdlocal.dll9.0.1518.048,416,98421-Jan-200604:30IA-64
Msmdpp.dll9.0.1518.06,473,43221-Jan-200604:31IA-64
Msmdpump.dll9.0.1518.06,527,70421-Jan-200604:31IA-64
Msmdredir.dll9.0.1518.06,072,53621-Jan-200604:31IA-64
Msmdsrv.exe9.0.1518.047,449,81621-Jan-200604:32IA-64
Msmgdsrv.dll9.0.1518.012,842,20021-Jan-200604:31IA-64
Msolap90.dll9.0.1518.07,686,36021-Jan-200604:31IA-64
Nsservice.exe9.0.1518.018,64821-Jan-200604:30x86
Osql.exe2005.90.1518.0123,09621-Jan-200604:30IA-64
Sqlaccess.dll2005.90.1518.0351,44821-Jan-200604:30x86
Sqlca.dll2005.90.1518.010,563,80021-Jan-200604:31IA-64
Sqldiscoveryapi_s.dll2005.90.1518.01,924,31221-Jan-200604:30IA-64
Sqlncli.dll2005.90.1518.05,383,44021-Jan-200604:31IA-64
Sqlservr.exe2005.90.1518.072,181,97621-Jan-200604:31IA-64
Txbestmatch.dll2005.90.1518.01,758,42421-Jan-200604:30IA-64

STATUS

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.

MORE INFORMATION

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:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbsql2005sp1fix kbsql2005engine kbprb kbHotfixServer kbsql2005presp1fix kbQFE kbpubtypekc KB912322 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.