Monitoring the Performance of Database Servers with IDERA SQL Diagnostic Manager for MySQL

It is essential to have access to detailed, real-time information on the performance of database servers and databases. Database performance problems affect the business-critical applications that they support. These issues were considered during a recent webinar featuring Patrick O'Halloran, senior sales engineer, IDERA, who discussed the use of SQL Diagnostic Manager for MySQL to ensure application responsiveness and database security.

Before these issues affect the organization it is important to use diagnostic tools to quickly locate and resolve performance issues in the early stages.

Monitoring and improving the performance of database environments is much more straightforward with quality monitoring applications and the right alerts in place.

O'Halloran, senior sales engineer, IDERA, spoke about the importance of continuously monitoring and analyzing MySQL and MariaDB to ensure application responsiveness and database security.

SQL Diagnostic Manager for MySQL is an IDERA tool that allows users to monitor MySQL and MariaDB databases, O’Halloran explained.

It is a low-overhead, low maintenance tool that, he said, is easy to install and easy to use. It is also powerful and flexible, and helps users pinpoint the instances, database, tables, and other activity in the environment that needs attention, he said.

The tool supports a variety of databases including:

  • Oracle MySQL Enterprise MySQL Server: 1, 5.5, 5.6, 5.7, 8.0
  • Oracle MySQL Cloud Service
  • MySQL Community Server: 5.1, 5.5, 5.6, 5.7, 8.0
  • MariaDB: 5.1, 5.2, 5.3, 5.5, 10.0, 10.1, 10.2, 10.3
  • Percona Server for MySQL: 5.1, 5.5, 5.6, 5.7
  • Galera Cluster for MySQL: 3
  • MariaDB Galera Cluster: 5.5, 10
  • Amazon RDS for MySQL, Amazon RDS for MariaDB, Amazon RDS for Amazon Aurora
  • Google Cloud SQL for MySQL

DM for MySQL is a Linux or Windows application that runs on a server. It is entirely self-contained and does not require any client agents, web servers, or any other software installed, O’Halloran said.

It connects to MySQL instances across the network and uses low-overhead and well-documented commands to gather information about the sessions, activity, and SQL statements that MySQL is executing, as well as server configuration and various logs.

The information gathered by DM for MySQL is stored in an internal SQLite database. This is a low-maintenance database that can grow to roughly 3-5GB of size per instance monitored. This depends on the amount of activity in the monitored server. The schema for DM for MySQL is documented, and both web-based and commandline utilities are available for SQLite, should you choose to access the data directly. Most users, however, will be showing screens, graphs, and other information through the web-based component of DM for MySQL. Users can connect to the DM for MySQL host via any common browser.

An archived on-demand replay of this webinar is available here.