When SQL Server is running in standard or mixed security mode, the counters used by SQL Performance Monitor make a connection using the special probe login ID (with no password). When the server is running in integrated security mode, the SQL Server counters will attempt to connect as either the logged on Windows NT user (if SQL Performance Monitor is running on the same machine as SQL Server), or as the LocalSystem account (if SQL Performance Monitor is running on a remote workstation).
You can force SQL Performance Monitor to make a trusted connection to SQL Server regardless of the server security mode by adding a Registry value with the Registry Editor tool (REGEDT32.EXE). In the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
add a value named PerfMonSecure, with a type of REG_DWORD and a value of 0x1. This will cause SQL Performance Monitor to request a trusted connection to SQL Server in the same security contexts, as described above, when SQL Server is running in integrated security mode. If the Registry value is not present or if the value is 0, SQL Performance Monitor will use the probe login ID.
Note that if you choose to configure SQL Server to listen on a named pipe other than the default pipe \\.\pipe\sql\query, SQL Performance Monitor will attempt to connect to SQL Server using the Windows NT-based machine name. To enable SQL Performance Monitor to access this SQL Server from a remote workstation using a trusted connection, you must add a DB-Library alias from that machine name to the alternate local pipe name. For example, if you configured SQL Server to listen on the named pipe \\.\pipe\sql\alternate, in the SQL Client Configuration Utility, use the Advanced tab to set the following:
| Server: | machine_name |
| DLL name: | Named Pipes |
| Connection string: | \\.\pipe\sql\alternate |
If SQL Server is not configured to listen on named pipes, you will not be able to run SQL Performance Monitor from a remote workstation via a trusted connection.