eG Monitoring
 

Measures reported by SqlAzuSessTest

In the database context, the connection between the user process and the server process is called a session. The server process communicates with the connected user process and performs tasks on behalf of the users. The SqlAzuSessTest test is used by an eG agent to track user activity related to a database server instance.

Outputs of the test : One set of results for each database instance:user combination on the target Microsoft SQL Azure Database server being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Total_sessions Indicates the total number of sessions that are currently open on the database instance for this user. Number A high value may indicate that there is a high load on the database instance.
Running_sessions Indicates the number of sessions that are currently running on the database instance for this user. Number  
Sleeping_sessions Indicates the number of sessions that were idle on the database instance for this user. Number  
Suspended_sessions Indicates the number of sessions initiated by this user on the database instance were suspended. Number  
Rollback_sessions Indicates the number of sessions that were rolled back for this user on the database instance. Number  
Dormant_sessions Indicates the number of sessions that were dormant for this user on the database instance. Number  
Pending_sessions Indicates the number of sessions that were pending for this user on the database instance. Number  
Blocked_sessions Indicates the number of sessions that were blocked for this user on the database instance. Number Blocking occurs when one session holds a lock on a resource that another session is requesting. As a result, the requesting session will be blocked - it will hang until the holding session gives up the locked resource. In almost every case, blocking is avoidable. In fact, if you find that your session is blocked in an interactive application, then you have probably been suffering from the lost update bug as well, perhaps without realizing it. That is, your application logic is flawed and that is the cause of blocking.

Ideally, the value of this measure should be zero. The detailed diagnosis capability, if enabled, lists all the blocked sessions of this database.