Although MyISAM has been the default storage engine for MySQL but its soon going to change with the release of MySQL server 5.5. Not only that, more and more people are shifting over to the Innodb storage engine and the reasons for that is the tremendous benefits, not only in terms of performance, concurrency, ACID-transactions, foreign key constraints, but also because of the way it helps out the DBA with hot-backups support, automatic crash recovery and avoiding data inconsistencies which can prove to be a pain with MyISAM. In this article I try to hammer out the reasons why you should move on to using Innodb instead of MyISAM.
Showing entries 1 to 1
Nov
16
2010
Posted by Ovais Tariq
on Tue 16 Nov 2010 11:47 UTC
Tags:
Tags:
innodb, Backups, foreign keys, transactions, locking, recovery, acid, clustered indexes, concurrency, row-level locking, crash recovery, throughput, Hot Backup, database resources, mysql resources, acid-compliant, adaptive hash indexing, background flushes, buffer pool, change buffer, data consistency, innodb resources, innodb vs myisam, read ahead, MySQL, Performance
Showing entries 1 to 1
Search
Top 20 Authors
Frederic Descamps (16)Valeriy Kravchuk (14)
Dave Stokes (9)
Mark Callaghan (9)
Jesper Krogh (8)
Krunal Lathiya (6)
Alena Subotina (5)
Jean-François Gagné (5)
Andrew Grimo (4)
Baron Schwartz (xaprb) (3)
Chris Calender (3)
Federico Razzoli (3)
Mahmud Ahsan (3)
Marco (3)
Simon Mudd (3)
Bhuvanesh R (2)
Evert Pot (2)
Ivan Ma (2)
Martijn Tonies (2)
Rik Prohaska (2)
Oracle MySQL Blogs
InsideMySQL.com (12)MySQL Server Team (12)
Oracle's MySQL Blog (12)
MySQL Support Team (9)
MySQL High Availability (6)
MySQL Release Engineering (5)
MySQL Workbench (2)