BUG: SQL Server Books Online Incorrectly States the Names of the SQL Server 2000 Counters for Named Instances (272433)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q272433
BUG #: 235555 (SHILOH)

SYMPTOMS

In the SQL Server Books Online topic Using SQL Server Objects, SQL Server object names are all listed as beginning with "SQL Server"; however, for SQL Server 2000 named instances the SQL Server object names actually show up in Performance Monitor as "MSSQL$InstanceName." If there is a SQL Server 7.0 instance or default SQL Server 2000 instance on the same computer as one or more SQL Server 2000 instances, the SQL Server 7.0 or default SQL Server 2000 instance counters show up as "SQL Server."

In this example, the SQL Server 2000 Instance Name is SQL1:
Books Online Counter Name            Actual SQL Server 2000 Counter Name for named Instance

SQL Server: Access Methods           MSSQL$SQL1:Access Methods
SQL Server: Backup Device            MSSQL$SQL1:Backup Device
SQL Server: Buffer Manager           MSSQL$SQL1:Buffer Manager
SQL Server: Cache Manager            MSSQL$SQL1:Cache Manager
SQL Server: Databases                MSSQL$SQL1:Databases
SQL Server: General Statistics       MSSQL$SQL1:General Statistics
SQL Server: Latches                  MSSQL$SQL1:Latches
SQL Server: Locks                    MSSQL$SQL1:Locks
SQL Server: Memory Manager           MSSQL$SQL1:Memory Manager
SQL Server: Replication Agents       MSSQL$SQL1:Replication Agents
SQL Server: Replication Dist.        MSSQL$SQL1:Replication Dist.
SQL Server: Replication Logreader    MSSQL$SQL1:Replication Logreader
SQL Server: Replication Merge        MSSQL$SQL1:Replication Merge
SQL Server: Replication Snapshot     MSSQL$SQL1:Replication Snapshot
SQL Server: SQL Statistics           MSSQL$SQL1:SQL Statistics
SQL Server: User Settable Object     MSSQL$SQL1:User Settable Object
				

CAUSE

A new format was needed to accommodate named instances in SQL Server 2000.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

MORE INFORMATION

Only counters for those SQL Servers started prior to opening Performance Monitor are available.

Modification Type:MajorLast Reviewed:10/3/2003
Keywords:kbbug kbpending KB272433