"Sounds like ISAM is more vulnerable to corruptions, but Inno DB will be trickier to repair.
Is that a fair summary" Yes that's one way of putting it.
The storage engine is the engine used to store and retrieve data. Luckily, in most cases, My ISAM table corruption is easy to fix.
Most popular storage engines are My ISAM and Inno DB. To fix a single table, connect to your My SQL database and issue a: If this doesn't help, there are a few additional tricks you can try. Multiple instances of My SQL This is pretty common.
If you're getting bombarded with queries and you need to be able to connect to the database to make some table changes, set a different port number in your /etc/file, start the database, make any changes, then update the port back to normal (master-port = 3306) and restart. Corrupt Inno DB tables Inno DB tables are my favorite.
Transactional, reliable and unlike My ISAM, Inno DB supports concurrent writes into the same table.
(It should start normally now) Step 6: Restore everything from your backup Calm Quiet, If you're running on a shared-server hosting platform, you can still export/import all data by using phpmyadmin (should be provided by your host).