myisam_tables
WARNING
Rule IDs: sch_002
Overview
- Purpose
- Presence of MyISAM user tables in the schema summary.
- Dynamic (MySQL 8.4 reference)
- Address by migrating storage engine or schema design — not one
SET GLOBAL. - Default value
- N/A
- Version and product notes
- MyISAM is discouraged for many production patterns versus InnoDB.
- Documentation
- Primary reference depends on product (MySQL, MariaDB, Percona, or OS documentation).
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- WARNING
sch_002: Convert MyISAM tables to InnoDB unless there is a specific reason (e.g., FULLTEXT in MySQL 5.5 — no longer needed in 5.6+).
Tuning guidance
- Recommended actions:
- Convert MyISAM tables to InnoDB unless there is a specific reason (e.g., FULLTEXT in MySQL 5.5 — no longer needed in 5.6+).
- Trade-offs: Schema issues (missing PKs, MyISAM tables) affect replication, backup, and InnoDB efficiency. Fixing schema requires application-level changes and testing, not just variable changes.
Example
ALTER TABLE my_table ENGINE = InnoDB; -- Test thoroughly before migrating production tables