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
Mark Callaghan (25)Frederic Descamps (15)
Dave Stokes (9)
Mikael Ronström (9)
Ahmed Bouchefra (6)
Bhuvanesh R (6)
parvez alam (5)
Sri Sakthivel Durai Pandian (5)
Vlad Mihalcea (4)
Selva (3)
Tony Darnell (3)
Valeriy Kravchuk (3)
Alena Subotina (2)
Andrew Grimo (2)
Art van Scheppingen (2)
Chandan Kumar (2)
Federico Razzoli (2)
Jean-François Gagné (2)
Olivier Dasini (2)
Colin Charles (1)