Checking and optimizing database tables in DirectAdmin

Identify a concrete reason for maintenance, such as an engine-reported table issue or a large deletion. Keep a verified backup, check free disk space and choose a quiet period. Large tables may need additional temporary space and can be locked during parts of an operation.

1. Open MySQL Management and select the intended database. Avoid selecting every database by default.
2. For a suspected table problem, run the available Check action and read the per-table output. Confirm the storage engine before interpreting the result.
3. Use Optimize only when appropriate for the engine and workload. For InnoDB, the server can implement this as a table rebuild, so review its cost and available space first.
4. Run one planned operation and wait for completion. Do not issue repeated optimization requests because the browser appears slow.
5. Compare the application behavior and relevant database measurements after maintenance. Investigate slow queries, indexes or resource limits separately if performance remains poor.

Review the full status and error output and test application reads and writes. Confirm that disk usage and service availability remain healthy. Keep before-and-after measurements if performance was the reason for the work.

If the job runs out of space, blocks production activity or reports corruption, stop broad maintenance and contact support with the table names and error. A table-engine message that optimization is implemented through a different operation is not automatically corruption. Do not use Repair repeatedly for InnoDB tables.

• Checking whether a DirectAdmin database repair is appropriate
• Downloading an SQL database backup from DirectAdmin
• Setting database-user privileges in DirectAdmin
• Changing a database-user password in DirectAdmin

• DirectAdmin: Mariadb MySQL
• MariaDB: Optimize Table