Making sense of db Health Check results - Powered By Kayako eSupport

Home | Register | Submit a Ticket | Knowledgebase | Troubleshooter

	Making sense of db Health Check results

Solution db Health Check allows you to check the overall health of the tables in your database. It checks to see if any of your tables have become broken and need to be repairs, and it checks to see if any of the tables have become fragmented and need to be optimized.

The output of db Helath Check will be as follows:
Checked: X
This is the number of database tables that were checked.

Repaired: No Tables Repaired, or a List of Table Names
If any of the tables need to be repaired then this displays the names of the tables that were repair, otherwise it shows "No Tables Repaired".
Ideally you never want to have to repair tables, but if you need to that is what db Health Check is for.

Optimized: No Tables Optimized, or a List of Table Names
If any tables need to be optimized then this is the names of the tables that were optimized. When you update or delete data from a table it can become fragmented, that is, it has spaces in the datafile which do not contain any actually data. Think of it as a Word document which has pages left blank for no apparent reason. (The reason is that either some data was just removed, or the data that was updated was too big to fill the space so it was moved)
Optimization goes and reorganizes the table so the blank spaces are gone. This improves performance.
Our optimization only runs on tables that are over a given threshold. (usually 4K, but able to be changed in the Configuration)
So a message of "No Tables Optimized" means that no tables were found that had free space within that threshold.
This is neither good or bad. Any table that is added to or edited or deleted from will eventaully need optimization. If you do not optimize tables regularily they can become broken more easily and need to be repaired.

So running the db Health Check once a week or once a month, depending on how active your database is, should help to ensure that your database runs efficiently.

Article Details

Article ID:

Created On:

19 Oct 2007 07:21 AM