Documentation forServer Configuration Monitor

Monitor a SQL database with SCM

You can now monitor databases for changes using Server Configuration Monitor (SCM), by running SQL queries to connect to any relational database such as Microsoft SQL Server, PostgreSQL, Oracle, or MySQL. SCM can collect data through SQL queries, then store that data and watch it for changes. This process enables SCM to track and alert you to changes made to user permissions, tables, indexes, views, stored procedures, scheduled jobs, and any other data you can gather using SQL queries.

Monitoring databases in SCM does not require an agent and can be performed on any type of node (Agent, WMI, SNMP, ICMP, and external). You must provide database account credentials required to monitor databases. Windows authentication is not supported. Along with supporting the use of credentials for databases, you can now add credentials for scripts and files. For more information on using credentials in SCM, see the SCM Administrator Guide topic, Specify element credentials in SCM.

Set up and install

To monitor a SQL element with Server Configuration Monitor (SCM), follow these instructions.

  1. Ensure that you can connect to the SQL database and that your SQL server is set to allow remote connections.
  2. The ODBC drivers are automatically installed with SCM 2020.2 or later unless FIPS is enabled on the system.

Configure SCM to monitor a Database query element

  1. Open SCM and go to the Server Configuration Monitor Settings page.
  2. Click the Profiles tab, and create new or edit an existing profile with a Database Query Element to test connectivity.
  3. Select, modify, or create a new connection string using the drop-down menu.
    Select Connection String from Drop-Down Menu
  4. Fill in or edit the element with the database query you want to test or that is collecting the desired configuration data.
  5. Specify SQL credentials and click TEST to test the connection.
    Specify SQL credentials and click TEST to test the connection

    Note: Due to security concerns, SolarWinds recommends that you avoid using username and password values in the Connection String. Instead, use the ${username} and ${password} macros along with specified credentials to ensure that sensitive values are properly secured.
  6. Select the node you want to test.
  7. After following these steps, the test should be successful. The success of the test is indicated on your test results page.

    Successful test result



    However, if there is an issue, an error message is displayed to help you start troubleshooting.

    Test results error

Out-of-the-box database profiles

There are new out-of-the-box profiles available to help you maximize this functionality:

  • MS SQL Server
  • PostgreSQL
  • MySQL

These out-of-the-box profiles provide a starting point for you to start monitoring your databases, and they can be customized to meet your organization's needs.

Additional notes on database monitoring

Users should take note of the following:

  • The SQL element in SCM can use only 32-bit ODBC drivers to connect to a database. This is not an issue for the databases, which use ODBC drivers provided by SolarWinds. However, if you use different drivers that are 64-bit, they would not work.

  • If you choose the Use Orion default credentials needed option and enter your login directly into the connection string, your credential information will be stored in the database in plaintext. Therefore, SolarWinds recommends that you use ${Username} and ${Password} macros and use credentials that are stored in the Orion Platform.

  • ODBC drivers are not installed with SCM if you have FIPS enabled on your system.