DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 944902 - Last Review: October 8, 2011 - Revision: 3.0

Hotfix Download Available
View and request hotfix downloads
 
Bug: #50002030 (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.

On This Page

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

Consider the following scenario. On a multiprocessor computer, you install more than one instance of Microsoft SQL Server 2005 that uses non-uniform memory access (NUMA) architecture. These instances compose a federated database server. In this scenario, when you run parallel queries, the CPU utilization of the server may increase to 100 percent. Additionally, the federated database server stops responding. If you run the following statement on one of the instances to examine the information about each request, the value of the wait_type column of many requests is CMEMTHREAD.
select * from sys.dm_exec_requests

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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

To apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed. For more information about how to obtain SQL Server 2005 Service Pack 2, 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.
SQL Server 2005, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3208.088,08808-Nov-200721:47x64
Chsbrkr.dll12.0.7822.01,694,05622-Jun-200710:51x64
Chtbrkr.dll12.0.7822.06,109,03222-Jun-200710:51x64
Databasemailprotocols.dll9.0.3208.046,10408-Nov-200721:47x86
Distrib.exe2005.90.3208.086,55208-Nov-200721:47x64
Dts.dll2005.90.3208.01,892,88808-Nov-200721:47x64
Dtsconn.dll2005.90.3208.0408,08808-Nov-200721:47x64
Dtspipeline.dll2005.90.3208.01,065,49608-Nov-200721:47x64
Fteref.dll12.0.7822.0433,15222-Jun-200710:51x64
Infosoft.dll12.0.7822.0621,41622-Jun-200710:51x64
Instorcl.sqlNot applicable153,77907-Nov-200713:18Not applicable
Korwbrkr.dll12.0.7822.0101,73622-Jun-200710:51x64
Langwrbk.dll12.0.7822.0236,90422-Jun-200710:51x64
Mergetxt.dll2005.90.3208.037,91208-Nov-200721:47x64
Microsoft.analysisservices.dll9.0.3208.01,217,56008-Nov-200720:31x86
Microsoft.sqlserver.connectioninfo.dll9.0.3208.0156,69608-Nov-200721:47x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3208.0115,73608-Nov-200721:47x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3208.0295,96008-Nov-200720:31x86
Microsoft.sqlserver.replication.dll2005.90.3208.01,832,98408-Nov-200721:47x64
Microsoft.sqlserver.servicebrokerenum.dll9.0.3208.042,00808-Nov-200721:47x86
Microsoft.sqlserver.smo.dll9.0.3208.01,606,68008-Nov-200721:47x86
Microsoft.sqlserver.smoenum.dll9.0.3208.0222,23208-Nov-200721:47x86
Microsoft.sqlserver.sqlenum.dll9.0.3208.0898,07208-Nov-200721:47x86
Msfte.dll12.0.7822.03,808,10422-Jun-200710:51x64
Msftefd.exe12.0.7822.099,17622-Jun-200710:51x64
Msftepxy.dll12.0.7822.0127,33622-Jun-200710:51x64
Msftesql.exe12.0.7822.0158,56822-Jun-200710:51x64
Msir5jp.dll5.0.2130.03,421,54422-Jun-200710:51x64
Mssqlsystemresource.ldfNot applicable524,28808-Nov-200717:19Not applicable
Mssqlsystemresource.mdfNot applicable40,239,10408-Nov-200717:19Not applicable
Nlhtml.dll12.0.7822.0191,84822-Jun-200710:51x64
Nls400.dll5.0.4217.014,101,35222-Jun-200710:51x64
Odsole70.dll2005.90.3208.090,13608-Nov-200721:48x64
Osql.exe2005.90.3208.085,52808-Nov-200721:48x64
Query9x.dll12.0.7822.068,45622-Jun-200710:51x64
Rdistcom.dll2005.90.3208.0828,44008-Nov-200721:48x64
Replmerg.exe2005.90.3208.0417,30408-Nov-200721:48x64
Replprov.dll2005.90.3208.0747,03208-Nov-200721:48x64
Replrec.dll2005.90.3208.01,012,24808-Nov-200721:48x64
Sac.exe9.0.3208.082,96808-Nov-200720:26x86
Sbmsmdlocal.dll9.0.3208.015,955,99208-Nov-200720:31x86
Sqlaccess.dll2005.90.3208.0357,40008-Nov-200721:48x86
Sqladhlp.exe2005.90.3208.066,07208-Nov-200721:48x64
Sqlagent90.exe2005.90.3208.0429,08008-Nov-200721:48x64
Sqlbrowser.exe2005.90.3208.0242,71208-Nov-200720:26x86
Sqlcmd.exe2005.90.3208.0338,45608-Nov-200721:48x64
Sqldiag.exe2005.90.3208.01,247,76808-Nov-200721:48x64
Sqldumper.exe2005.90.3208.068,63208-Nov-200720:26x86
Sqldumper.exe2005.90.3208.083,99208-Nov-200721:48x64
Sqlmaint.exe2005.90.3208.092,69608-Nov-200721:48x64
Sqlsac.exe2005.90.3208.01,246,23208-Nov-200720:26x86
Sqlservr.exe2005.90.3208.039,596,56808-Nov-200721:48x64
Sqlsqm.exe9.0.3208.0128,02408-Nov-200720:26x86
Sqlsqm.exe9.0.3208.0128,02408-Nov-200721:48x86
Sqlwep.dll2005.90.3208.090,64808-Nov-200720:26x86
Sqlwep.dll2005.90.3208.0123,41608-Nov-200721:48x64
Sqlwtsn.exe9.0.3208.099,35208-Nov-200720:26x86
Sqlwtsn.exe9.0.3208.099,35208-Nov-200721:48x86
Sqsrvres.dll2005.90.3208.082,96808-Nov-200721:48x64
Ssradd.dll2005.90.3208.050,71208-Nov-200721:48x64
Ssravg.dll2005.90.3208.051,73608-Nov-200721:48x64
Ssrmax.dll2005.90.3208.048,15208-Nov-200721:48x64
Ssrmin.dll2005.90.3208.048,15208-Nov-200721:48x64
Ssrpub.dll2005.90.3208.034,84008-Nov-200721:48x64
Sysdbupg.sqlNot applicable510,62228-Aug-200704:40Not applicable
Tablediff.exe9.0.3208.087,06408-Nov-200721:48x86
Thawbrkr.dll12.0.7822.0209,76822-Jun-200710:51x64
Xmlfilt.dll12.0.7822.0271,20822-Jun-200710:51x64
Xpadsi90.exe2005.90.3208.069,14408-Nov-200721:48x64
Xpstar90.dll2005.90.3208.0549,91208-Nov-200721:48x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This hotfix is scheduled to be included in Cumulative Update Package 5 for SQL Server 2005 Service Pack 2. Cumulative Update Package 5 introduces new global trace flag 8048. If you cannot resolve this issue by applying this hotfix, you can try to use global trace flag 8048 to resolve the issue after you install Cumulative Update Package 5. You can enable the global trace flag when the SQL Server service starts. Global trace flag 8048 converts all the memory objects that are partitioned by a NUMA node into memory objects that are partitioned by CPU. Global trace flag 8048 may remove contention from the CMEMTHREAD wait type on a symmetric-multiprocessing (SMP) computer that has many CPUs or on a NUMA computer that has many CPUs for each node.

Note If you enable this global trace flag, we recommend that you monitor performance after you apply any other hotfixes or cumulative update packages. You may experience performance decreases after you apply other hotfixes or cumulative update packages.

For more information about the naming schema for 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

APPLIES TO
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
Keywords: 
kbautohotfix kbsql2005engine kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB944902
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support