This article describes the following about this hotfix release:
| The issues that are fixed by this hotfix package |
| The prerequisites for applying the hotfix package |
| Whether you must restart the computer after you apply the hotfix package |
| Whether the hotfix package replaces any other hotfix package |
| The files that are contained in the hotfix package |
Consider the following scenario. A server has been running for a while. Then, you run a query in Microsoft SQL Server 2005. In this scenario, the query performance may be slow.
Additionally, when you query the
sys.dm_os_wait_stats dynamic management view, you may notice that there are many rows in which the values of the
wait_type column are SOS_RESERVEDMEMBLOCKLIST or DBCC MEMORYSTATUS. This situation indicates that many multipage allocations exist.
This problem occurs only on 64-bit servers that have more than 16 gigabytes (GB) of physical memory.
Service pack information
To resolve this problem, obtain the latest service pack for 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 now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
You must have Microsoft SQL Server 2005 Service Pack 1 installed to apply this hotfix.
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
Restart requirement
You do not have to restart the computer after you apply this hotfix. However, after you apply this hotfix, you must add the
-T8030 option as a SQL Server startup parameter to enable trace flag 8030. Then, you must restart the SQL Server service for the hotfix to take effect.
For more information about how to add SQL Server startup parameters, see the "To start an instance of SQL Server with startup options" section of the "How to start an instance of SQL Server (SQL Server Configuration Manager)" topic in SQL Server 2005 Books Online.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
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.
| File name | File version | File size | Date | Time | Platform |
|---|
| Msvcp80.dll | 8.0.50727.42 | 1,385,472 | 14-Oct-2005 | 07:05 | IA-64 |
| Msvcr80.dll | 8.0.50727.42 | 1,484,800 | 14-Oct-2005 | 07:05 | IA-64 |
| Osql.exe | 2005.90.1543.0 | 123,168 | 26-Apr-2006 | 18:03 | IA-64 |
| Osql.rll | 2005.90.1399.0 | 14,552 | 14-Oct-2005 | 09:07 | Not applicable |
| Sqldiscoveryapi.dll | 2005.90.1543.0 | 1,924,384 | 26-Apr-2006 | 18:04 | IA-64 |
| Sqlse.rll | 1.1.12.0 | 43,008 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 52,736 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 49,952 | 26-Apr-2006 | 18:04 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 52,224 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 51,712 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 43,008 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 43,008 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 51,712 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 47,104 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 44,032 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 43,008 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlse.rll | 1.1.12.0 | 51,200 | 08-Nov-2005 | 11:36 | Not applicable |
| Sqlrun_sql.msp | Not applicable | 55,922,688 | 26-Apr-2006 | 22:53 | Not applicable |
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 SQL Server 2005 Service Pack 2.
