#1
  1. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Mar 2004
    Posts
    165
    Rep Power
    11

    Converting to innodb file per table - convert all tables to innodb?


    Hi,

    I'm going to be converting our dbs to innodb file per table. Right now, each db is a mix of innodb and myisam tables. Should I convert all dbs to pure innodb (and dump, drop, and rebuild to get file per table) or just the dbs where I 'm concerned about performance? In other words, can I leave the non-mission critical, low-usage dbs as a mix of innodb and myisam?

    Thanks,
    Mike
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Oct 2013
    Posts
    158
    Rep Power
    10
    In other words, can I leave the non-mission critical, low-usage dbs as a mix of innodb and myisam

    Databases that are a mix of MyISAM and InnoDB is basically a disaster waiting to happen, MyISAM doesn't enforce referential integrety or transactions so that's not good.

    So if you can; move all databases to InnoDB completely.
  4. #3
  5. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Mar 2004
    Posts
    165
    Rep Power
    11
    Originally Posted by Vinny42
    Databases that are a mix of MyISAM and InnoDB is basically a disaster waiting to happen, MyISAM doesn't enforce referential integrety or transactions so that's not good.

    So if you can; move all databases to InnoDB completely.
    Thanks, Vinny. I was looking for an excuse to get lazy.

IMN logo majestic logo threadwatch logo seochat tools logo