FastDomain - MySQL Repair and Optimize Tables in phpMyAdmin
 

FastDomain Web Hosting Help

MySQL Repair and Optimize Tables in phpMyAdmin

Occasionally the MySQL database may run slower than desired. This issue can be fixed quickly through phpMyAdmin.

Note: Please back up any database on the account before making changes)

  1. Log in to your FastDomain cPanel account.
  2. Under the Database Tools click on phpMyAdmin.
  3. On the left will be a list of databases. Select the one to repair/optimize.
  4. This will load all of the tables in your database into the right side. At the bottom of this list, check the "Check All" checkbox.
  5. Just to the right of the Check All link, select the "Repair" option in the drop-down list.
  6. This will list all the tables, with "OK" listed next to them. When this is done, look up to the top of the page and click on the "Structure" tab.
  7. Once the process has finished the page will revert back to step 4.
  8. Click "Check All" again, and then choose "Optimize" in the drop down menu.
Now the process is done!

Many MySQL errors can be fixed by this process. It is recommended to perform these steps frequently to keep any database in good condition.

(Note: If you are using InnoDB as a storage engine, we have noticed an issue regarding database size: For various reasons, it occasionally occurs that memory allocated to a customer for database usage is not released when it is no longer required by the database. This memory does not appear as in use when database size is viewed using phpMyAdmin, but since it is still allocated to the customer account, the server-side administrative tools will include it in calculations of overall database memory usage and determinations of whether or not an account has exceeded the database memory limits specified in the Terms of Service. The easiest way to free this "hidden" memory is to export the database information, completely clear the database, and re-import the information. This will cause phpMyAdmin and the server-side tools to report the actual database usage and prevent account deactivation due to the "hidden" memory usage. The repair/optimize function in phpMyAdmin will not correct this issue. The server-side tools report complete memory usage which is the information required to determine overall performance of the server, and that is why the server-side tools are used to determine usage for ToS compliance purposes. phpMyAdmin does not correctly report all memory usage allocated to the account and is therefore not used for these calculations.



Was this resource helpful?

Did this resolve your issue?


Please add any other comments or suggestions about this content:





Recommended Help Content

Guidance on adding tables to your mySQL database in phpMyAdmin
Knowledgebase Article 115,288 views tags: mysql phpmyadmin

How do I import a backup of my database (.sql file) using phpMyAdmin?
Knowledgebase Article 783,065 views tags: database mysql phpmyadmin

A repository of information on how you can manage your database by using the phpMyAdmin interface.
Knowledgebase Article 376,695 views tags: commands database mysql phpmyadmin

Related Help Content

Optimizing MySQL: Queries and Indexes Article 1 of 4 Courtesy of: Ian Gilfillan Badly defined or non-existent indexes are one of the primary reasons for poor performance, understanding and then fixing
Knowledgebase Article 221,944 views tags: indexes mysql optimize optimizing queries query

This article will show you how to rename a database table in phpMyAdmin.
Knowledgebase Article 323,680 views tags: databases mysql phpmyadmin

Optimizing MySQL: Queries and Indexes Article 4 of 4 Courtesy of:Ian Gilfillan Most systems need to be highly optimized for selects - take a news site which performs millions of queries per day, but w
Knowledgebase Article 216,885 views tags: cpu exceeded index indexes mysql optimize optimizing queries query

A step by step guide on how to manipulate data in your mySQL tables using phpMyAdmin
Knowledgebase Article 200,235 views tags: databases mysql phpmyadmin

Optimizing MySQL: Queries and Indexes Article 3 of 4 Courtesy of: Ian Gilfillan Ordering by surname is a common requirement, so it would make sense to create an index on surname. But in this example o
Knowledgebase Article 222,358 views tags: cpu exceeded index indexes mysql optimize optimizing queries query

Optimizing MySQL: Queries and Indexes Article 2 of 4 Courtesy of: Ian Gilfillan Some knowledge of how indexes work allows you to use them more efficiently. Firstly, note that when you update a table w
Knowledgebase Article 188,887 views tags: indexes mysql optimize optimizing queries query

A guide to duplicating a MySQL database using phpMyAdmin
Knowledgebase Article 244,136 views tags: databases mysql phpmyadmin

A tutorial on how to perminately delete columns from your mySQL database using phpMyAdmin
Knowledgebase Article 189,552 views tags: Plesk cpanel databases mysql phpmyadmin