SQL Server processor
This function is used to view the different processes and current locks in the database when the database used is SQL Server™.
Important remark
Warning, this type of function facilitates, via a user interface homogenous with the software, the launch of live procedures dedicated to a database admin. It is made to be launched by such an admin (usually called DBA).
To be used optimally, the user should be familiar with the functioning of databases and their optimization.
Conversely, an inappropriate use of the function can be problematic for the performances of the system and might compromise the utilization of the software.
Screen management
This function is used to view the processes and the locks corresponding to these processes in the database.
These elements are presented in two tabs : the first provides a list of the processes, the second gives the list of locks.
The function is used to identify the blocking locks. After verification of the blocking and blocked processes, it will be possible to kill the blocking process.
Header
Used to identify the characteristics of the database used.
Database (field BDDNAM) |
Name of the database. |
Version (field VER) |
Version number of the database. |
field VERDES |
Description of the database version. |
Tab Processes
On entry to this function, the processes connected to the current folder are displayed by default.
If the processes in all the solution folders are required, it is necessary to modify the Processes filter.
If the process display sort is to be modified, it is necessary to modify the Process sort and Direction.
It will then be necessary to refresh the display using the bottom of the screen.
This screen is made up of two sections :
Processes
This first section contains a grid that presents the processes running on the database.
Display options
This section is used to modify the filter options and the process sort.
The filter is used to restrict the processes display and as a result the display of the locks.
It will be necessary to refresh the display using the button at the bottom of the scree to take into account the new display options.
ID of process (field SPID) |
Identifier for the process in the database |
Connection user (field LOGNAM) |
Name of the database user |
Database (field DBNAM) |
Name of the database. |
Connection date (field LOGDAT) |
Connection date |
field LOGHOU |
Connection time |
Status (field STA) |
Status of the connection |
Application (field APP) |
Program in the process of execution. |
Command (field CMD) |
Command actually executed |
Last execution (field LASDAT) |
Date of the last execution for an SQL instruction on the connection |
field LASHOU |
Time of the last execution for an SQL instruction on the connection |
Host machine (field MAC) |
Name or the computer or the machine (defined by the operating system) from which the user is connected. |
Process host (field OSPRO) |
Identifier for the process on the machine (defined by the operating system). |
CPU (field CPU) |
Total UC time for the execution of the process |
Memory (field MEMUSE) |
Number of cache pages for the procedures actually allocated to the processes. A negative number indicates that the process liberates the memory allocated to another process. |
Phys IO (field PHYIO) |
Total number of write and read operations on the disk for the process. |
ID of blocking process (field BLOCKID) |
Identifier for the blocking process |
Block number 2
Filter process (field FLT) |
Used to restrict or not the list of processes. It is possible to display
|
field FILLER0 |
Sort of processes (field TRI) |
Used to sort the list of processes. There is the possibility to specify the sense of the sort. |
Sign (field TYPTRI) |
Detail | ||||||||||||||
Field descriptions
Block number 1
Last SQL instruction
|
Used to view the text for the last SQL instruction for the process.
Used to immediately kill the selected process.
Only a database user having the role sysadmin or processadmincan carry out this action. It will therefore be necessary to give the name of the user having sufficient rights plus their password.
Tab Locks
The second tab displays the list of locks in place and pending on the database that corresponds to the processes in the first tab.
This is used to distinguish in the case of blocking locks:
- which process is blocking
- which process is blocked and which is the process that it blocks.
Grid
ID of process (field SPID) |
Identifier for the process in the database |
Database (field DBNAM) |
Name of the database. |
User (field LOGNAM) |
Name of the database user |
Host machine (field MAC) |
Name or the computer or the machine (defined by the operating system) from which the user is connected. |
Owner (field OBJOWN) |
Owner of the object currently being locked. |
Object (field OBJNAM) |
Name of the object or the transaction currently being locked. |
Index (field INDNAM) |
Name of the index being locked. |
Type (field TYPLCK) |
Locked resource type. Possible values: 1. NUL = NULL resource (not used). |
Resource (field RES) |
Textual description of a locking resource |
Method (field MODE) |
Locking request method. This column corresponds to the locking method of the requestor and represents the method granted, the conversion method or the pending method. Possible values: 0 = NULL. No access is accorded to the resource. Serves as reserved space. |
Block status (field LCKSTA) |
Status of the locking request. Possible values: 1 = Granted |
Delay of SPID (field WAIT) |
Identifier for the blocking process |
Detail | ||||||||||||||
Field descriptions
Block number 1
Last SQL instruction
|
Used to view the text for the last SQL instruction for the process.
Specific Buttons
Refresh |
This button, also accessible using the short cut, used to refresh the display of the tabs. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
"Verify the parameterization of the solution from the console (solution.xml file)."
Required information cannot be recovered from the solution.xml file. The parameterization of the solution is incomplete and it is necessary to complete it using the configuration console.