MySQL is known for its ease-of-use, performance, and scalability. The versions prior to MySQL 5.5 have MyISAM as their default database storage engine. In MySQL 5.5, the default settings have been changed as InnoDB becomes the default database storage engine. This change has brought a handful of significant improvements in the lives of database users and administrators. Some of the major benefits of using InnoDB tables include ACID transactions, Referential integrity, and Crash recovery.
With the increased hard drive and memory capacity, performance and data availability have become the topmost user priorities. Some of the real world benefits of using InnoDB tables are listed below:
Despite these benefits, various environmental factors may cause corruption in your InnoDB database. Let us have a glance at some of the potential database corruption scenarios:
In a majority of such cases, InnoDB performs crash recovery. It has numerous ‘undo logs’ to store all incomplete database transactions. During crash recovery, these transactions are rolled back to make the database logically consistent.
In the event of an operating system or disk crash, you can go for media recovery. In order to perform media recovery, you require an updated backup of the database files and MySQL’s archived binlog files. The ‘binlog’ is needed to redo all database operations after the backup was performed.
May 1, 2013
April 16, 2013