Prev | Current Page 151 | Next

Marc Delisle

"Mastering phpMyAdmin 2.11 for Effective MySQL Management"


Outages may occur on the server, leaving some tables in a damaged state.
Using the Operations sub-page, we can perform various operations, but not every
operation is available for every table type:
Check table: Scans all rows to verify that deleted links are correct. Also, a
checksum is calculated to verify the integrity of the keys; we should get an
'OK' message if everything is all right.
Analyze table: Analyzes and stores the key distribution; this will be used
on subsequent JOIN operations to determine the order in which the tables
should be joined.
Repair table: Repairs any corrupted data for tables in the MyISAM and
ARCHIVE engines. Note that the table might be so corrupted that we cannot
even go into Table view for it! In such a case, refer to the Multi-Table
Operations section for the procedure to repair it.
Optimize table: This is useful when the table contains overheads. After
massive deletions of rows or length changes for VARCHAR fields, lost bytes
remain in the table. phpMyAdmin warns us in various places (for example,
in the Structure view) if it feels the table should be optimized. This operation
is a kind of defragmentation for the table. In MySQL 4.x, this operation
works only on tables in the MyISAM, Berkeley (BDB), and InnoDB engines.
In MySQL 5.x, it works only on tables in the MyISAM, InnoDB, and
ARCHIVE engines.


Pages:
139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163