There are a few circumstances where one will not want to run with only MyISAM tables. In this case, it can be beneficial to completely disable InnoDB.
As InnoDB has become more prevalent, disabling it in MySQL requires a little more effort than before.
In MariaDB 10.0, you can still completely disable it as you have done in the past (just add the –skip-innodb option, specify default-storage-engine=MyISAM, and comment out other InnoDB options):
Alternatively, instead of –skip-innodb, you can instead use “innodb=OFF”:
In MySQL 5.6, the –skip-innodb option has been deprecated (though still currently works), and since InnoDB is the new “default” storage engine, you must set both “default-storage-engine” and the new “default-tmp-storage-engine” options to “MyISAM”. If you do not set the latter, you instance will not start, and the error log will simply complain that “Unknown/unsupported storage engine: InnoDB” and you won’t easily identify why:
2014-11-08 18:47:28 13524 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-11-08 18:47:28 13524 [ERROR] Aborting
So, if you want to disable InnoDB in MySQL 5.6, you’ll need to specify the following:
For reference, this last part is documented in the manual here, but I felt a post was appropriate given the obscurity of this overall issue.
Also, if you disable InnoDB in MySQL, you may see an extraneous message in your error log, as described here. Also, in both MySQL and MariaDB, you’ll likely see a few strange messages after running mysql_upgrade, which I discuss in more detail here.
Hope this helps.