SQL Response Test

The responsiveness of a database to SQL queries is not only indicative of the health of the database server, but also the efficiency of the queries. A well-tuned database is one that quickly responds to SQL queries, and a well-built SQL query is one that succeeds in retrieving the desired results from the database and that too, in record time. The SQLResponseTest monitors SQL queries from start to finish, and reports the status of the query execution and its responsiveness. This way, administrators are proactively notified of failed queries and queries that take too long to execute, so that root-cause diagnosis is instantly initialized.

Target of the test : A database server

Agent deploying the test : An internal agent

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

Configurable parameters for the test

Parameter

Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port at which the application listens.

JDBC Driver

Specify the JDBC driver that is used to access the database. The table below lists the JDBC drivers that correspond to some of the most popular database servers that are monitored by eG Enterprise. Refer to this table whenever in need.

Database	Driver
Oracle	oracle.jdbc.driver.OracleDriver
MS SQL	net.sourceforge.jtds.jdbc.Driver
Informix	com.informix.jdbc.IfxDriver
Sybase	com.sybase.jdbc2.jdbc.SybDriver
MySql	org.gjt.mm.mysql.Driver

Connection URL

Specify the JDBC URL for the database. The URL format is JDBC driver specific. The table below lists the JDBC URLs for some of the most popular database servers that are monitored by eG Enterprise. While configuring this test for any of the database servers in this table, you can specify a URL of the corresponding format.

Database	Driver
Database	URL Format
Oracle	jdbc:oracle:thin:@{host}:{port}:{instance}
MS SQL	jdbc:jtds:sqlserver://{host}:{port}/{database}
Informix	jdbc:informix-sqli://{host}:{port}/{database}:informixserver={instance}
Sybase	jdbc:sybase:Tds:{host}:{port}/{database}

If the target database is not in the above list, then follow the steps given below:

Download the JDBC driver of the new database from the database vendor.
Copy the relevant java package files (jar or zip) into the {EG_AGENT_INSTALL_DIR}\lib directory (on Windows; on Unix, this will be the /opt/egurkha/lib directory).
If a Unix agent is executing this test, then simply proceed to restart the eG agent. In case of a Windows agent however, edit the debugoff.bat file in the {EG_AGENT_INSTALL_DIR}\lib directory to manually set the Classpath value. Then, execute debugoff.bat so that the agent service is reinstalled on Windows with the new classpath settings.
Next, login to the eG administrative interface and configure this test with the JDBC Driver and Connection URL that corresponds to the new database.

User

The name of the User who is vested with the privilege to execute the configured query.

Password

The password of the specified User.

Confirm Password

Confirm the password by retyping it in the Confirm Password text box.

Query

Specify the query to be executed and monitored.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Query status	Indicates whether the configured query has been successfully executed.	Boolean	The value of 1 indicates successful execution, and 0 indicates failure. In case of query failure, you can use the detailed diagnosis of this measure, if enabled, to view the errors that caused the query to fail; troubleshooting thus becomes easier.
Query time	Indicates the time taken to execute the query and retrieve results.	Secs	An abnormally high value is a cause for concern, and warrants further investigation.