SQL Long Running Queries Test

This test reports 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.

One set of results for each database on the Microsoft SQL server monitored

Target of the test : A Microsoft SQL server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each database on the Microsoft SQL server monitored

Note:This test will execute only on Microsoft SQL Server 2005 (or above).

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed. By default, this is set to 60 minutes.
Host	The IP address of the Microsoft SQL server.
Port	The port number through which the Microsoft SQL server communicates. The default port is 1433.
User	If a Microsoft SQL Server 7.0/2000 is monitored, then provide the name of a SQL user with the Sysadmin role in this text box. While monitoring a Microsoft SQL Server 2005 or above, provide the name of a SQL user with all of the privileges outlined in User Privileges Required for Monitoring Microsoft SQL server.
Password	Specify the password corresponding to the mentioned user.
Confirm Password	Confirm the password by retyping it.
Instance	Enter the name of a specific Microsoft SQL instance that is to be monitored against this parameter. The default value of this parameter is “default”. To monitor a Microsoft SQL instance named “CFS”, enter this as the value of the Instance parameter.
Domain	By default, none is displayed in the Domain text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the Domain can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the Domain text box, specify the Windows domain in which the managed Microsoft SQL server exists. Also, in such a case, the User name and Password that you provide should be that of a user authorized to access the monitored SQL server.
ISNTLMV2	In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 (“NTLMv2”) was concocted to address the security issues present in NTLM. By default, the ISNTLMV2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL host. Set this flag to Yes if NTLMv2 is enabled on the target host.
IsPassive	If the value chosen is Yes, then the Microsoft SQL server under consideration is a passive server in a SQL cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable" by the agent if the server is not up.
SSL	By default, the SSL flag is set to No, indicating that the target Microsoft SQL server is not SSL-enabled by default. To enable the test to connect to an SSL-enabled Microsoft SQL server, set the SSL flag to Yes.
Force Strict Encryption	Specify Yes if you want to enforce strict encryption for communication. Default is No.
Hostname in Certificate	Specify the hostname that the certificate is issued for.
Truststore Filename	This parameter is applicable only if SSL-enabled channel is used for communication to the target SQL server, if not, set this parameter to none. Truststore is used to store certificates from Certified Authorities (CA) that verify and authenticate the certificate presented by the server in an SSL connection. Therefore, the eG agent should have access to the truststore where the certificates are stored to authenticate and connect with the target server and collect metrics. For this, first extract the certificates from the server into the following default location /opt/egurkha/jre/lib/security/egmqsslstore.jks.
Truststore Password and Confirm Password	If a Truststore File name or file path is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File. Confirm the password by retyping it in this text box.
Top N Query	Specify the number of queries which you want to be included in monitoring of long running queries.
Elapsed Time (Seconds)	In the ELAPSED TIME text box, specify the duration (in seconds) for which a query should have executed for it to be regarded as a long running query. The default value is 10.
Exclude Info	By default, this is set to none, indicating that the test will monitor all the databases on the Microsoft SQL server by default. To exclude specific databases from the monitoring scope of this test, provide a comma-separated list of databases in the EXCLUDE INFO text box.
Exclude Command	Specify the command you want to exclude from the list of long running queries. For example “backup” queries are included in the long-running queries list, they will be automatically excluded based on this parameter. As a result, only balance queries will be displayed in the UI. By default, this parameter set to “NONE”.
Exclude User	Specify the user you want to exclude from the list of long running queries. By default, this parameter is set to "none". However, you have the option to configure this parameter if they want to exclude specific users.
Timeout (Seconds)	Specify the duration (in seconds) for which this test should wait for a response from the SQL server in the Timeout text box. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 120 seconds.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurement made by the test
Measurement	Description	Measurement Unit	Interpretation
Avg elapsed time:	Indicates the average time taken by queries to execute on this database.	Secs	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.	Secs