Differences between MySQL InnoDB/MyISAM/merge/bdb/heap

Official accurate explanation

· MyISAM: the default MySQL plug-in storage engine, which is one of the most commonly used storage engines in Web, data warehousing, and other application environments. Note: by changing the storage_engine configuration variables, you can easily change the default storage engine of the MySQL server.

· InnoDB: used for transaction processing applications. It has many features, including ACID transaction support.

· Bdb: it can replace InnoDB's transaction engine and support commit, rollback, and other transaction features.

· Memory: stores all data in Ram and provides extremely fast access in environments where reference and other similar data need to be quickly searched.

· Merge: Allows MySQL DBAs or developers to logically combine a series of equivalent MyISAM tables and reference them as one object. It is suitable for vldb environments such as data warehousing.

· Archive: provides a perfect solution for storing and retrieving a large number of rarely referenced historical, archived, or security audit information.

· Federated: connects multiple separated MySQL servers and creates a logical database from multiple physical servers. It is very suitable for distributed environments or data mart environments.

· Cluster/NDB: MySQL's cluster-based database engine is especially suitable for applications with high-performance search requirements. Such search requirements also require the highest normal working time and availability.

· Other: other storage engines include CSV (referencing files separated by commas as database tables), blackhole (used to temporarily prohibit database application input ), and the example engine (which can help you quickly create a custom plug-in storage engine ).

Remember that you do not have to use the same storage engine for the entire server or solution. You can use different storage engines for each table in the solution. This is very important.