I am changing an old MySQL database table which is still in MyISAM. I'd like to change it to InnoDB, but I don't know whether it can cause problems and it's a pretty important table so I don't want to break anything.

So my question: can it cause problems when I convert a MyISAM table to InnoDB?

  • Maybe perform some testing on your test server? You do have one? MyISAM is being deprecated in any case. – Vérace Mar 22 '17 at 10:56
  • Hi joshua, the answer you looking for is here dev.mysql.com/doc/refman/5.7/en/… – Peter R Mar 22 '17 at 10:58
  • @Vérace where did you find hat MyISAM is being deprecated? I have never heard of this before. – ypercubeᵀᴹ Mar 22 '17 at 20:31
  • I got it from here. Bill Karwin was a Percona (?) consultant and is widely regarded as an SQL guru. – Vérace Mar 23 '17 at 1:10
  • Version 8.0 removes MyISAM; they announced it at the Oracle conference last fall. (I think I saw Bill there.) – Rick James Mar 23 '17 at 22:52

Yes, it can cause a number of troubles. However, troubles are rare.

All the 'troubles' I know of are listed here.

(Do not change tables in the databases mysql or information_schema or performance_schema; that will cause serious trouble.)

  • Thanks, good answer. Don't think it'll give me much problems. And no, I wasn't planning on changing anything to mysql, information_schema or performance_schema. Cheers! – Joshua Bakker Mar 23 '17 at 8:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.