eG Help

When any conditions cause a server to exhaust its resources, it fails to handle incoming requests leading to server over load. Any performance degradation or unavailability of the database servers can severely impact the performance of the entire service, often causing customer dissatisfaction and lost business revenue. Continuous monitoring of the SQL Azure database servers for overload due to sessions initiated by applications are hence imperative. This is where the SqlAzuSesActTest helps database administrators!

This test monitors the sessions initiated by each application on the SQL Azure server, and reports the level of activity each application has imposed on the server.

Outputs of the test : One set of results for the SQL Azure server being monitored

Measurement	Description	Measurement Unit	Interpretation
Active_request_count	Indicates the rate at which the application is sending requests to the server.	Requests/Sec
Blocked_request_count	Indicates the number of requests of the application that are currently blocking.	Number	Ideally, the value of this measure should be 0. If the measure reports a non-zero value, then you can use the detailed diagnosis of the Blocked processes measure of the SQL System Processes test to identify the exact query that is responsible for the blocking.
Blocking_request_count	Indicates the number of requests of this application that are currently being blocked.	Number	Ideally, the value of this measure should be 0. If the measure reports a non-zero value, then you can use the detailed diagnosis of the Blocked processes measure of the SQL System Processes test to identify the exact query that is responsible for the blocking.
No_of_Process	Indicates the total number of processes executed currently by this application on the server.	Number	The detailed diagnosis of this measure is used to view the complete details of the session. This includes the session ID, the user who has initiated the session, the current status of the session, the elapsed time, CPU time, open cursor count,active request count,blocking/blocked request count, the count of disk reads and writes, and the count of logical reads performed by the session. These information enables you to know how resource intensive the session is and how much I/O load has been generated by the session.
Open_cursor_count	Indicates the total number of cursors executed currently by the application on the server.	Number	In terms of a server overload, you can compare the value of this measure across the applications to identify the sessions that are responsible for increasing the transaction load on the server.
Open_resultset_count	Indicates the number of resultsets that are currently open on the server for this application.	Number
Open_transaction_count	Indicates the total number of transaction executed currently by the application on the server.	Number	In terms of a server overload, you can compare the value of this measure across the applications to identify the sessions that are responsible for increasing the transaction load on the server.