Occasionally we have customers with MyISAM storage engine approaching us to migrate their database to InnoDB, MyISAM is great if you are just an application like web content management system with no multi-user concurrency challenges but what if you are building an highly transactional data web property ? InnoDB is much preferred for such situations, InnoDB provides Row-level locking (Oracle like) for consistent reads on an multi-user concurrent user high performance database application. InnoDB also guarantees maximum data integrity by supporting FOREIGN KEY, We captured below few interesting points to remember while migrating your database from MyISAM to InnoDB :<\/p>\n

\n
• Data of InnoDB tables is stored in *.ibd files, deleting those files will permanently corrupt your database<\/li>\n
• InnoDB tables consumes more storage space than MyISAM tables .<\/li>\n
• Unlike MyISAM, InnoDB is a transactional database engine. In any typical MyISAM environment, MySQL DBAs don’t worry much about COMMIT (to finalize the changes) and ROLLBACK (to undo the changes) statements.<\/li>\n
• By default, InnoDB tables use setting autocommit=0 and this avoids unnecessary I\/O when you are issuing long transactions with consecutive INSERT, UPDATE or DELETE statements, This allows you to issue a ROLLBACK statement to recover lost or garbled data if you make a mistake on the mysql command line or in an exception handler in your application .<\/li>\n
• The reliability and scalability features of InnoDB\u00a0require more disk storage than equivalent MyISAM tables.\u00a0You might change the column and index definitions slightly, for better space utilization, reduced I\/O and memory consumption when processing result sets, and better query optimization plans making efficient use of index lookups.<\/li>\n
• InnoDB tables build your data on disk to optimize queries based on primary keys, Each InnoDB table has primary key index called clustered index that organizes the data to minimize disk I\/O for primary key lookups.<\/li>\n<\/ul>\n

  Convert existing MyISAM to InnoDB table (quick and direct)\u00a0<\/strong><\/p>\n

  ALTER TABLE table_name<\/em> ENGINE = InnoDB;<\/p>\n

  Transfer Data from MyISAM to InnoDB table<\/strong><\/p>\n

  INSERT INTO innodb_table\u00a0<\/em>SELECT * FROM\u00a0misaim_table\u00a0<\/i>ORDER BY primary_key_columns\u00a0<\/em><\/p>\n

  We recommend indexes creation for InnoDB tables after loading data, loading data on indexed table will seriously impact performance. The same principle applies if you have UNIQUE constraints on secondary keys. Increase size of system variable innodb_buffer_pool_size\u00a0<\/em>to 80% of available physical memory for optimal performance.<\/p>\n","protected":false},"excerpt":{"rendered":"

  Occasionally we have customers with MyISAM storage engine approaching us to migrate their database to InnoDB, MyISAM is great if you are just an application like web content management system with no multi-user concurrency challenges […]<\/a><\/p>\n<\/div>","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,2,15],"tags":[23,5,16],"yoast_head":"\n