Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Monitor MySQL with SAM - Setup/Configuration

Monitor MySQL with SAM - Setup/Configuration

Updated March 1, 2017


For SAM to monitor MySQL, there are some prerequisites that need to be completed before the application monitor will work. 


All SAM versions


  1. Make sure that you have a user that can connect to the MySQL database and that your MySQL server is set to allow remote connections. Some installed MySQL only listen on by default.
  2. Download both the 32 and 64 bit msi driver here.
  3. Install both on your main Orion server and any Additional Polling Engines you have.
  4. Once installed, open ODBC Data Source (32-bit) and click on the Drivers tab.

    c:\windows\syswow64\odbcad32.exe shows you 32-bit drivers and 

    c:\windows\system32\odbcad32.exe shows you 64-bit drivers

    Make note of the MySQL Driver name. In this screenshot,  it is MySQL ODBC 5.1 Driver. This may vary depending on the version of the MySQL driver installed.



  1. Open SAM and find and edit the MySQL template.
  2. Expand the first component to test with.
  3. Edit the Connection String and insert Driver={} with the name of the MySQL Driver you noted in step 3 of prerequisites.
  4. Make sure you define Credentials for monitoring too, those would be a MySQL user.
  5. Test the connection, as long as everything is in place the test should be successful. If not, then click details in the error and see what it gives and where you might need to start troubleshooting.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified