See Also: Main Page - Database Administration - Troubleshooting SQL Server

Finding the Instance Name from Task Manager

When running multiple instances of SQL Server on one server it can be difficult to identify which instance is using excessive resources.

Task Manager shows:

Figure 1 - Task Manager

Where each sqlservr.exe represents an instance. Finding the instance name requires the Process Identifier (PID) which is not shown by default in Task Manager.
The PID needs to be selected via Task Manager –> View –> Select Columns menu item.

Figure 2 - Select Columns from Task Manager

In this case PID 2652 was using more CPU. There are two options available to track down the instance name:

SQL Server Configuration Manager

On clicking on the SQL Server Services in SQL Server Configuration Manager, the details of SQL Server and related services along with the Process ID of each service is listed. The SQL Server Instance name is listed as SQL Server (InstanceName).

Figure 3 - Configuration Manager

SQL Server Error Log

In SQL Server 2000, SQL Server Configuration Manager is not available. The information regarding the Process ID can be obtained through the SQL Server Error Log.

Figure 4 - Error Log

Once you know the instance using excessive resources further investigation of the instance is required to identify the cause.

Adapted from http://www.sqldbadiaries.com/2011/01/04/find-the-sql-server-instance-name-using-task-manager/

Author

Pradeep Adiga

Pradeep is a Subject Matter Expert (SME) for SQL Server with one of the biggest MNCs in Information Technology field, where he works with highly critical OLTP systems and over 50 TB data warehouse. Pradeep has over a decade of IT experience, performing SQL Server Database Administration, System Administration. Pradeep specializes in problem management, high availability of MS SQL Server databases and provides technical leadership for SQL Server DBAs.

His online presences include:

• Blog: http://www.sqldbadiaries.com/
• Twitter: http://twitter.com/pradeepadiga