wolstech Posted April 20, 2014 Share Posted April 20, 2014 InnoDB tends to trash itself more frequently when MySQL crashes. MyISAM can crash too, but it is more stable than innodb is, and repair is often easier if something does happen. Link to comment Share on other sites More sharing options...
McCozza Posted April 21, 2014 Author Share Posted April 21, 2014 Hi Wolstech, Thanks v.much. I have now managed to restore the website that gets used a lot after taking your advice above. I'll wait until mysql issues are solved to drop the redundant database. Or maybe I can delete all the table records from the redundant database if I start running into space issues? Cheers Nick Link to comment Share on other sites More sharing options...
wolstech Posted April 21, 2014 Share Posted April 21, 2014 The innodb tables are read-only, so you won't be able to remove their records. If you have any MyISAM tables mixed in with the innodb tables though, you can remove the records from those particular tables (or drop the MyISAM table entirely.) Link to comment Share on other sites More sharing options...
Recommended Posts