ipMonitor 6.1
Edit QA SQL Monitor
< BackIndexNext >


The ODBC/SQL Quality Assurance Monitor tests the ability to log into to an external database, perform a query, and retrieve the results. It effectively ensures that:
  1. There are enough "connection handles" available.
  2. The specified account can log into the database.
  3. The database server can process SQL statements.
  4. The server can distribute the correct result set.
Open Database Connectivity is an environment intended for generic database access and use. It seamlessly supports cross-platform solutions so you can test any database -- provided that you have Windows NT drivers installed.

Any account and password information entered into the Monitor configuration interface is transmitted to the database resource and the resource itself decides if there is enough permission for the database to be used.

The user-defined SQL statement can be any valid statement that will return a result set. To reduce the strain on the specified resource, a limit can be applied to the number of rows that will be retrieved / analyzed.

To ensure that the correct result set is returned, the following two methods can be used together:

  1. Row counting
  2. Text searching or matching a single column

When text searching or matching a column, you can specify the name of the column or the column number.

Note: To use this monitor type you must have 32-bit ODBC drivers installed at the time that ipMonitor is started.

To configure a DSN (Data Source Name), visit "ODBC 32" in the Windows NT control panel. If the Data Source Name you want to use doesn't appear in the selector dialog it is most likely because the DSN was configured as a USER DSN in a different account space other than that which ipMonitor uses.

Important: In order to monitor Oracle 8i structures, the Oracle 8i Client must be installed and properly configured in addition to the DSN. The Oracle 8i Client is a required element to make ODBC connections.

This Monitor:

  • Considers the specified resource unavailable after a specified number of seconds.
  • Persistently tests the resource at specified intervals.
  • Disallows testing during a maintenance period.
  • Waits for a specified number of failures to occur before starting alerts.
  • Switches testing intervals, from "responding correctly" to "not responding correctly". Configurable intervals allow you to test more or less aggressively in the event of failure.
  • Stops alerting after a specified number of alerts.
  • Has a placeholder for a WinNT Service Name or any other information required by a recovery script.
Please refer to Last Status by Monitor Type for details regarding Last Status codes displayed for this monitor in the Monitor Status reports.