Show TOC

Database ProcessesLocate this document in the navigation structure

Use

This screen provides two views on database processes. Processes are known as Sessions, with corresponding connections and requests. All the threads needed by SQL Server, including all connections made by SAPwork processes are shown.

Display this screen by executing the transaction DBACOCKPIT in the GUI Command Field and navigate to Performance →Database Processes.

Features

Data can be presented in several ways. Sessions can be grouped by their ID, or can be shown grouped by the hostname/ work process id of the client program. Only active requests, or currently executing sessions can be displayed by pressing the Active Request button or checkbox. An active session has a record in the data management view sys.dm_exec_requests only when it is executing. The other option is to display all sessions and connections, even those that are currently not active. In addition, the sessions of the sqlservr.exe process can be included or excluded from the display by using the menu item SQL Sessions → SQL Engine Sessions or in some cases, by selecting the Include SQL Engine Processes checkbox.

Sessions can be filtered out based on three criteria: the SQL Server login, the application server, or the Work Process number (Program Name). When one of these filters is changed, the process data is retrieved. If no filtering is desired, use the <any> selection from the drop-down menu.

The SQL Statement associated with a session and connection can be shown via the SQL Statement button. Currently running requests can also have their plans displayed via the Explain button.

There are two views of the data available. The first view was developed to provide a simplified view of critical metrics, while the second view presents additional data from the data management views of sessions, connections, and requests.

There is a reset/since reset functionality to measure a specific period. The reset captures a data snapshot, which is in effect until another reset is executed, even if the data view is changed. Using the Refresh button causes the display to present values accumulated since database startup.