ADO - User Experience monitor
The ADO - User Experience (SQL Query) monitor (also known as the Database Experience monitor) connects to an SQL server or supported data source. The monitor performs a query, retrieves data, and analyzes the results to ensure they are correct.
Create an ADO - User Experience (SQL Query) monitor
You can create the monitor using the ADO-User Experience (SQL Query) Wizard. The wizard helps you configure a monitor with the least amount of initial input by automatically creating the SQL statement using the information you provide. It tests the parameters you enter along the way to make sure that the monitor will work as expected before you transition to a production environment.
If you prefer additional control over the process, you can clone an existing ADO monitor and apply any required configuration changes.
The ADO - User Experience (SQL Query) monitor requires MDAC 2.6 or later installed on the ipMonitor host computer. MDAC 2.5 and earlier do not support Named Instances, which are used when more than one instance of SQL Server is running on a machine.
See Monitor the IBM DB2 database using ipMonitor for details about monitoring this database using this monitor.
ODBC drivers for monitoring a MySQL database
You can monitor a MySQL database on a Microsoft Windows Server system using one of the following drivers:
- ODBC Driver from MySQL downloaded from the MySQL Connectors website
- Microsoft OLE DB Provider for ODBC downloaded from the Microsoft Data Access Components (MDAC) Downloads website
If the computer hosting ipMonitor is running a 64-bit operating system, use the 64-bit MyODBC driver or the 64-bit version of MDAC 2.8 released with the Windows Server 2003 64-bit operating system.
The test results display the total number of rows returned to the monitor for analysis.
You may have an occurrence where the monitor generates the following error:
Error: ADO User Experience monitor error: 0x80004002
The ADO User Experience monitor can only monitor client machines running Microsoft Data Access Components (MDAC) 2.6 SP2 or later. If the client machine is running an earlier version, the monitor generates this error.
To resolve this issue, download and install the latest MDAC version from Microsoft. See the Microsoft Docs website for details.