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

Consider the following scenario. You run a tool that uses SQL Server performance counters to collect performance data against 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 counter data is not updated after you start the instance of SQL Server. Additionally, the tool displays static performance data instead of the actual real-time data from the instance of SQL Server. This problem occurs until you restart the tool.

The tool calls the Sqlctr90.dll file to access 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.

Note After you apply this fix, the DLL will be able to switch between static mode and server interactive mode.

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

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

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: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: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: