If Aria storage engine (previously called Maria) is the "new" MyISAM, which supports transaction and automatic crash recovery:
- Why still use MyISAM ?
- Should changing storage engine from MyISAM to Aria be a problem? (lose index or something)
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this communityIf Aria storage engine (previously called Maria) is the "new" MyISAM, which supports transaction and automatic crash recovery:
It is very interesting this question would come up because a similar question was asked back in January 2011 ( When is the right time to use MariaDB instead of MySQL, and Why? ). Giving thought to that 16-month-old question and how I answered it in April 2011, here are my answers to your immediate questions:
Why still using MyISAM ?
MyISAM still has features that are unique and useful for small datasets and read slaves in HA setups
Converting to Fixed Row Format creates bigger tables but increases query performance in terms of
Full Faith and Confidence
To changes storage engine from MyISAM to Maria should it be a problem? (lose index or something)
If you mysqldump the data and the schema into two separate files, you can always import data into table with either the MyISAM or Aria storage engines. Just keep around the data only mysqldump to be sure.