Use the Fragmented Tables health check in Mini DBA to review MySQL and MariaDB configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for storage layout, growth, or space-management choices that can cause avoidable outages or uneven performance.
Storage and file-layout problems can create sudden outages or long-running waits. This check makes those risks visible before they block user work.
Move files away from fragile locations, pre-size growth-heavy files, fix uneven growth, add capacity, and review retention or cleanup jobs. Avoid shrinking files unless the growth was a one-time exception.
Keep evidence of current size, free space, growth history, retention settings, and who approved any storage or file-layout change.
Treat a failure as high priority on production systems because it can affect recoverability, availability, or security posture.
Prevent repeat failures by reviewing capacity trends alongside alert history. If the same check returns after each fix, treat it as a sizing or design issue rather than a one-off maintenance task.
Add this page to the operational runbook for MySQL and MariaDB environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.