Article ID: 948344 - Last Review: August 25, 2008 - Revision: 1.0
FIX: Performance data is not updated when you run a tool that uses SQL Server performance counters to collect performance data for an instance of SQL Server 2005
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.
Consider the following scenario. You run a tool that uses Microsoft SQL Server performance counters to collect performance data for an instance of Microsoft SQL Server 2005. For example, you run System Monitor together with SQL Server performance counters. You start the tool before you start the instance of SQL Server. In this scenario, the performance data is not updated after you start the instance of SQL Server. Additionally, the tool displays static performance data instead of displaying the actual real-time performance data from the instance of SQL Server. This problem occurs until you restart the tool.
The tool calls the Sqlctr90.dll file to access the SQL Server performance counters. This DLL works in static mode or in server interaction mode. In static mode, the DLL cannot communicate with SQL Server. The DLL can communicate with SQL Server only in server interaction mode. However, the DLL cannot switch from static mode to server interaction mode after the Sqlctr90.dll file is loaded.
This hotfix is a SQL Server 2005 Service Pack 1-based hotfix. If you have SQL Server 2005 Service Pack 2 installed, do not apply this hotfix. Instead, use the resolution that is described in the following Microsoft Knowledge Base article:
949115
(http://support.microsoft.com/kb/949115/
)
Performance counter data is not updated when you run a tool that uses SQL Server performance counters to collect performance data against an instance of SQL Server 2005
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
SQL Server 2005 Service Pack 1
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:
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 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.
After you apply this hotfix, the DLL can switch between static mode and server interactive mode.
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