Thank you for your help. Even though the solution I had to use was formulated by me, it contains a lot of bits and pieces of help from here.
I am concerned about running a healthy system so I did read the comparison and description links that were provided. I am, however, also concerned about the future.
As was so very seriously demonstrated to me personally, live production servers will fail, hard even. In this instance it appears that it died at such the wrong time that the crash recovery system inherent in InnoDB actually caused more problems for me than they would have potentially solved.
For me, the fact that this option (innodb_data_home_dir
) to move what is seemingly an essential file for the InnoDB engine to a location counter-intuitive of data storage even merely existing is a great cause for concern. What if this happened again on a default installation of MySQL like the one I encountered for Windows? What would happen on a partial/failed update/reinstall of MySQL? What about (possibly forced) migrations!!! Even if future install releases, whether by the MySQL dev. team themselves or distro specific, never again specify a location different than would be expected, the potential for it to all go horribly wrong still exists.
What also concerns me about InnoDB is that in this instance to successfully mount the database onto a new system and ultimately recover the underlying data to a usable state I had to delete
files. Although, after reading the suggested articles to understand why, of which is now partial, it still seems a bit backwards to me.
Don't get me wrong, I do ascribe to aforementioned adage of "If it ain't broke, don't fix it", but also do ascribe to the old "Murphy's Law" axiom of "Whatever can go wrong, will go wrong." My first hands-on and deep-in-the-trenches experience with InnoDB goes something like this: "It broke and went very wrong."
After today I have come to the personal conclusion that, no-doubt, InnoDB has probably saved others from some probably very serious crashes, but I surmise that if I had been using MyISAM, this thread would have ultimately been much much
shorter, whether either by MyISAM completely failing to retain the database on unexpected hardware failure or by just being plain easier to move to another system.
I am posting this not really to rag on InnoDB because of my one and only bad experience (I acknowledge the implications of that) on recovering a database but rather to inform that my decision is not entirely reactionary and completely uninformed. Ultimately, for me, MyISAM might even be better with regards to phpBB anyway: