Skip to content
⚡ MySQL Advisor

MySQL • MariaDB • Percona

MySQL Advisor

MySQL Configuration, Performance, Schema & Upgrade Advisor

Tools for MySQL DBAs to review configuration, troubleshoot performance and InnoDB issues, and plan version upgrades. Analyze server configuration and runtime metrics, investigate SHOW ENGINE INNODB STATUS, and check upgrade readiness before moving to another version.

Core workflows include: Configuration Advisor, SEIS Advisor, Schema Advisor, and Upgrade Advisor.

Core workflows

Configuration Advisor

Analyze SHOW GLOBAL VARIABLES, SHOW GLOBAL STATUS, pt-summary, and pt-mysql-summary for performance, security, replication, memory, I/O, and configuration issues.

Analyze configuration

SEIS Advisor

Turn SHOW ENGINE INNODB STATUS into structured diagnostics covering transactions, locks, semaphores, buffer pool activity, redo, I/O, deadlocks, and row operations.

Open SEIS Advisor

Schema Advisor

Review CREATE TABLE statements or a mysqldump --no-data file for primary key design, duplicate and redundant indexes, foreign key mismatches, InnoDB row size, and schema conditions that block an upgrade.

Review your schema

Upgrade Advisor

Compare your current MySQL configuration with a target version and identify deprecated, removed, and version-specific settings before an upgrade.

Check upgrade readiness

MySQL Configuration Advisor

Input console
or
or
or
or
Or collect from a read-only MySQL connection
Collect data from MySQL
CAPTCHA
Automate with the API. Run configuration, InnoDB status and schema analysis from your terminal or CI, with one API key. JSON or Markdown, no database access.
About MySQL Advisor

MySQL Advisor: Configuration, InnoDB Diagnostics, Schema Review and Upgrade Readiness

MySQL Advisor started as a MySQL configuration analyzer and has grown into a broader DBA toolkit. It now covers the core DBA workflows of reviewing configuration, investigating InnoDB behavior, reviewing schema and table design, and checking upgrade readiness before a MySQL version change.

The tools work from diagnostic output you already have. You can paste or upload SHOW GLOBAL VARIABLES, SHOW GLOBAL STATUS, pt-summary, pt-mysql-summary, or SHOW ENGINE INNODB STATUS, depending on the workflow. An optional collector can fetch the configuration inputs from a read-only MySQL connection.

Core workflows

MySQL troubleshooting rarely fits into one category. A server can have a reasonable configuration and still be suffering from lock contention, redo pressure, transaction buildup, internal semaphore contention, or an operational issue that configuration review will not reveal.

MySQL Configuration Advisor: Performance and Configuration Analysis

Configuration Advisor analyzes the output of SHOW GLOBAL VARIABLES and SHOW GLOBAL STATUS, with optional pt-summary and pt-mysql-summary reports for additional operating-system and MySQL context.

It reviews areas such as InnoDB memory, redo and durability, I/O and concurrency, connections and per-thread memory, binary logging and replication, schema and table health, security, logging and monitoring, operating-system limits, PXC/Galera, and Group Replication.

Findings are prioritized by severity and explain the variable or metric involved, why it matters, and what evidence or configuration change should be considered. It is intended as a fast first-pass review, not a replacement for workload profiling, load testing, or application-level investigation.

Browse the MySQL variable reference to see the settings behind the checks.

SHOW ENGINE INNODB STATUS Advisor (SEIS)

SEIS Advisor is the InnoDB diagnostics tool in MySQL Advisor. It reads SHOW ENGINE INNODB STATUS and turns the debug-style output into a structured analysis of the sections that matter during troubleshooting.

Depending on the capture, that can include transactions and history, lock waits and deadlocks, semaphore and mutex contention, buffer pool activity, file I/O, redo and checkpoint behavior, change buffer or adaptive hash index information, and row-operation counters.

The aim is not simply to explain every line. It is to separate useful evidence from noise, show where a finding came from, distinguish observation from interpretation, and point to the related variables or diagnostic queries that can provide stronger evidence.

For the underlying concepts, see the InnoDB Status Field Guide.

MySQL Schema Advisor: Table Design and Index Review

Schema Advisor works on table definitions rather than runtime output. Give it a single CREATE TABLE, a set of them, or a dump taken with mysqldump --no-data, and it reviews each table for primary key design, duplicate and redundant indexes, foreign key type and charset mismatches, InnoDB row size headroom, character set consistency, and common design antipatterns.

It also flags the schema conditions that block a major version upgrade, such as reserved words that became reserved at the target version, so a table design problem is caught before the upgrade window rather than during it.

Where a definition alone cannot settle a question, the finding says so and gives you the query to run on the server. Open Schema Advisor to review a set of tables.

MySQL Upgrade Advisor: Upgrade Readiness Checks

Upgrade Advisor is designed for the point before a major or significant MySQL version change. Give it the current configuration and a target version, and it checks for deprecated, removed, and version-specific variables and related compatibility concerns.

The goal is to catch configuration surprises before the maintenance window. It complements, rather than replaces, the checks you should perform with the official MySQL upgrade tooling and your own application and workload validation.

Open Upgrade Advisor to start a target-version review.

What can you use MySQL Advisor for?

  • Configuration review: get a fast second opinion on a new or inherited MySQL server.
  • Performance investigation: correlate configuration, runtime counters, and InnoDB status evidence.
  • Incident troubleshooting: investigate locks, transactions, semaphores, buffer pool behavior, redo pressure, and other InnoDB signals.
  • Schema review: check table definitions for primary key, index, foreign key and row size problems before they reach production.
  • Upgrade planning: review configuration changes before moving to a target version.
  • Fleet and CI checks: use the API to run repeatable configuration, InnoDB status and schema analysis across servers.
  • Consulting and support: produce a report that can be shared with another DBA, engineering team, or customer.

Supported databases and environments

The analyzers are designed around MySQL-compatible environments and adapt their checks to the detected flavor and version.

  • MySQL: 5.6, 5.7, 8.0, and 8.4 LTS.
  • MariaDB: 10.x and 11.x branches supported by the relevant analyzer.
  • Percona Server for MySQL: including Percona-specific configuration and features where applicable.
  • Percona XtraDB Cluster (Galera): configuration and cluster-related checks.
  • MySQL Group Replication: configuration and flow-control related checks.

Version awareness matters because a setting, status field, or recommendation can change meaning between releases. Where behavior differs, the analyzer should use the detected version rather than treating all MySQL-family servers the same.

Why use MySQL Advisor?

  • No installation
  • No agent or SSH
  • Paste or upload diagnostics
  • Read-only analysis (for diagnostic input)
  • Version-aware
  • Export reports (HTML, Markdown, Word)
  • REST API (automation and CI)
  • Multiple diagnostic workflows

How MySQL Advisor works

The workflow is deliberately simple:

  1. Collect evidence: paste or upload the relevant MySQL output, or use the optional read-only collector for configuration data.
  2. Detect the environment: identify the MySQL-family flavor and version where the input supports it.
  3. Analyze the evidence: apply version- and flavor-aware checks to the inputs available for that workflow.
  4. Explain the finding: show the evidence, reasoning, severity, and recommended next step rather than only producing a verdict.

Because SHOW ENGINE INNODB STATUS and other status outputs are point-in-time diagnostics, repeated samples and correlation with Performance Schema, Information Schema, status variables, system metrics, or workload data may still be needed to confirm persistence and root cause.

Automate MySQL analysis with the API

Configuration Advisor, SEIS Advisor and Schema Advisor each have a REST endpoint, using the same API key, for CI pipelines and fleet-wide reviews. Responses are JSON, with a Markdown report option on the configuration and SEIS endpoints. The same principle applies: send diagnostic output or table definitions, receive structured findings, and keep the database outside the analysis path.

Read the API usage guide or request an API key.

Frequently asked questions

What does MySQL Advisor do?

MySQL Advisor is a DBA toolkit with core workflows: Configuration Advisor for configuration and runtime checks, SEIS Advisor for SHOW ENGINE INNODB STATUS, Schema Advisor for table design and index review, and Upgrade Advisor for target-version readiness. It is designed to turn diagnostic output into evidence-based recommendations and next steps.

What is SEIS Advisor?

SEIS Advisor is the InnoDB diagnostics tool in MySQL Advisor. It parses SHOW ENGINE INNODB STATUS and organizes the output into findings across transactions, locks, semaphores, buffer pool, redo, I/O, deadlocks, row operations, and other sections present in the capture.

What does SEIS Advisor analyze?

SEIS Advisor analyzes the sections present in a SHOW ENGINE INNODB STATUS capture, including transactions and history, lock waits and deadlocks, semaphore and mutex contention, buffer pool activity, file I/O, redo and checkpoint information, change buffer or adaptive hash index information, and row-operation counters.

It shows the evidence behind a finding and points to related variables or diagnostic queries when the capture alone is not enough to establish the root cause.

Does MySQL Advisor connect to my database?

Analysis does not require a database connection. You can paste or upload diagnostic output and analyze it directly. There is also an optional collector for SHOW GLOBAL VARIABLES and SHOW GLOBAL STATUS; when used, the connection is opened from the MySQL Advisor server with credentials you provide for that request.

The collector is read-only and does not perform writes, locks, or schema changes. If your database is private, paste the output instead.

What is Schema Advisor?

Schema Advisor is the table design tool in MySQL Advisor. It reads CREATE TABLE statements or a mysqldump --no-data file and reviews each table for primary key design, duplicate and redundant indexes, foreign key compatibility, InnoDB row size, character sets, and common design antipatterns. It parses the SQL, it never executes it.

What does Schema Advisor check?

Tables without a primary key, wide or UUID-as-text primary keys, duplicate and redundant indexes, unique keys that repeat the primary key, nullable columns in unique keys, indexed long text columns, foreign keys whose column type, signedness or character set does not match the parent, non-InnoDB engines and old row formats, InnoDB row size against the 65,535 byte and 8,126 byte limits, utf8mb3 and mixed character sets, float for money, zero date defaults, the 2038 TIMESTAMP boundary, reserved words at the target version, and identifiers over 64 characters.

Do I need to send my data to review a schema?

No. Schema Advisor only needs definitions. mysqldump --no-data produces the CREATE TABLE statements with no rows, so no application data leaves your server. The input is parsed and discarded once the response is sent.

Which databases and versions are supported?

MySQL 5.6, 5.7, 8.0, and 8.4 LTS; MariaDB 10.x and 11.x; Percona Server for MySQL; Percona XtraDB Cluster (Galera); and MySQL Group Replication, with support varying by workflow and detected version.

What does Upgrade Advisor check?

Upgrade Advisor compares your current configuration with a target version and highlights deprecated, removed, and version-specific variables and other configuration changes that should be reviewed before the upgrade.

When should I use Upgrade Advisor?

Use Upgrade Advisor before a planned MySQL version change, especially when moving between major or significant release families. It is intended as an early configuration review so deprecated, removed, or version-specific settings can be identified before the maintenance window.

It complements, rather than replaces, the official MySQL upgrade checks, application testing, and workload validation.

How are the recommendations generated?

The configuration analyzer uses version- and flavor-aware heuristic checks across areas such as InnoDB, I/O, connections, replication, security, logging, operating-system limits, and clustering. Each finding includes the relevant evidence, reasoning, severity, and recommendation.

Is it safe to use on production systems?

The analysis workflows are read-only. They operate on diagnostic output you provide and do not make database changes. The optional collector only runs the two read-only configuration commands described above.

Is there an API?

Yes. Configuration Advisor, SEIS Advisor and Schema Advisor each have a REST endpoint, using the same API key. Responses are JSON, with a Markdown report option on the configuration and SEIS endpoints. Useful for CI pipelines and fleet-wide checks. See the API usage guide or request an API key.

Is MySQL Advisor only for configuration review?

No. Configuration review is one part of the toolkit. MySQL Advisor also includes SEIS Advisor for InnoDB diagnostics, Schema Advisor for table design and index review, and Upgrade Advisor for version-readiness checks, with room to add more DBA workflows over time.

Who is MySQL Advisor for?

It is aimed at DBAs, developers who own their databases, DevOps and platform engineers, consultants, support engineers, and anyone who needs a practical first-pass analysis of a MySQL-family environment.