eG Monitoring
 

Measures reported by SqlAzuLgRunQryTest

Nothing can degrade the performance of the server like a resource-hungry or a long-running query! When such queries execute on the server, they either hog almost all the available CPU, memory, and disk resources or keep the resources locked for long time periods, thus leaving little to no resources for carrying out other critical database operations. This can significantly slowdown the database server and adversely impact user experience with the server. To ensure peak performance of the SQL Azure server at all times, such queries should be rapidly identified and quickly optimized to minimize resource usage. To monitor the time taken by each database for executing queries, and also to reveal which query is taking too long to execute, eG Enterprise offers the SqlAzuLgRunQryTest.

This test monitor the time taken by each database for executing queries, and also reveals which query is taking too long to execute. This way, resource-intensive queries to a database can be quickly isolated.

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

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Avg_elapsed_time Indicates the average time taken by queries to execute on this database. Seconds If the value of this measure is very high, it could either indicate that the database is unable to process the queries quickly or that one/more queries to the database are taking too long to execute. Improper indexing and fragmented tables in the database are common causes for slowdowns at the database-level. Besides the above, queries that are improperly structured can also take time to execute. The longer a query executes on the database, higher would be the resource consumption of that query. It is therefore imperative that such resource-intensive queries are quickly isolated and fine-tuned, so as to prevent degradations in the performance of the database server.

Using the detailed diagnosis of this measure, you can rapidly identify the resource-intensive queries to the database.
Max_elapsed_time Indicates the maximum time taken by the queries to this database. Seconds