Important note: The information in the article below is outdated and shown for reference purposes only. Please use the ADO SQL v2 sensor (available as of PRTG version 16.2.24) to monitor databases using an ADO connection.

Monitoring (Almost) Any SQL Server Through ADO with PRTG Network Monitor

Using a custom EXE sensor script for PRTG you can monitor any SQL server using ActiveX Data Objects (ADO) and the PowerShell scripting language.

There are two usage scenarios for this script:

• Using this script you will be able to monitor any data source with PRTG that is accessible through ADO, including many database servers (e.g. SQL Server, Oracle, IBM DB2, MySQL, Sybase, Informix, Interbase, Firebird) as well as data files (Excel, Access, SQlite, Foxpro, Filemaker). Even Sharepoint, MS Project, Active Directory and Exchange are possible.
• Although PRTG has built-in native sensors for the most used databases (Microsoft, MySQL and Oracle SQL servers) it can sometimes be helpful to use the ADO interface for monitoring.

How to do it

• First you need the "connection string" which tells ADO where and how to connect. The website http://www.connectionstrings.com/ offers predefined connections string for over 50 different data sources.
• For Windows XP/2003/Vista/2008 R1: Download and install PowerShell on the machine that will run the script (your core server or a system running the associated probe). PowerShell is already included in Windows 7 and 2008 R2.
• Download the script Demo Powershell Script - Connecting to database with ADO.ps1 from the PRTG Addons Google Code project and place it into the following folder either on your PRTG core installation (if you want to use the LocalProbe) or on a Remote Probe System. Note: The script as well the Google Code project are deprecated and not available anymore! \prtg network monitor\custom sensors\exe
• Edit the settings in the "Parameters" section of the ps1 file for your needs.
• In PRTG's web interface: create a new Custom EXE Sensor and select the filename mentioned above.

That's it, you should now see the sensor's results.

Security Issues

It's a good practice to not enter passwords, parameters, etc. directly into your script. Instead, you can use the parameter field in PRTG to hand over these values to your script when calling it.

Information about signing Powershell scripts and the Execution Policy for scripts can be found in the following external resources:

• PowerShell Script Signing
• PowerShell Security

See Also

How do I correctly configure credentials for ADO SQL sensors?