{"id":12253,"date":"2023-11-11T01:26:28","date_gmt":"2023-11-11T08:26:28","guid":{"rendered":"https:\/\/www.mysqltutorial.org\/?page_id=12253"},"modified":"2023-11-13T00:35:57","modified_gmt":"2023-11-13T07:35:57","slug":"mysql-storage-engines","status":"publish","type":"page","link":"https:\/\/www.mysqltutorial.org\/mysql-administration\/mysql-storage-engines\/","title":{"rendered":"MySQL Storage Engines"},"content":{"rendered":"\n

Summary<\/strong>: in this tutorial, you will learn various MySQL storage engines<\/strong>. It is essential to understand the features of each storage engine in MySQL so that you can use them effectively to maximize the performance of your databases.<\/p>\n\n\n\n

Introduction to MySQL Storage Engines<\/h2>\n\n\n\n

In MySQL, a storage engine is a software component responsible for managing how data is stored, retrieved, and manipulated within tables. A storage engine also determines the underlying structure and features of the tables.<\/p>\n\n\n\n

MySQL supports multiple storage engines, each has its own set of features. To find the available storage engines on your MySQL server, you can use the following query:<\/p>\n\n\n

SELECT<\/span> \n  engine<\/span>, \n  support \nFROM<\/span> \n  information_schema.engines \nORDER<\/span> BY<\/span> \n  engine<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Output:<\/p>\n\n\n
+--------------------+---------+\n| engine             | support |\n+--------------------+---------+\n| ARCHIVE            | YES     |\n| BLACKHOLE          | YES     |\n| CSV                | YES     |\n| FEDERATED          | NO      |\n| InnoDB             | DEFAULT |\n| MEMORY             | YES     |\n| MRG_MYISAM         | YES     |\n| MyISAM             | YES     |\n| ndbcluster         | NO      |\n| ndbinfo            | NO      |\n| PERFORMANCE_SCHEMA | YES     |\n+--------------------+---------+\n11 rows in set (0.02 sec)\n<\/code><\/span>Code language:<\/span> plaintext<\/span> (<\/span>plaintext<\/span>)<\/span><\/small><\/pre>\n\n\n
The query returns 11 storage engines in the engine column and whether it is supported or not in the support column.<\/p>\n\n\n\n
If the support column is YES<\/code>, it means that the corresponding storage engine is supported, or NO<\/code> otherwise. <\/p>\n\n\n\n
If the value in the support column is DEFAULT<\/code>, which means that the storage engine is supported and used as the default. <\/p>\n\n\n\n
Alternatively, you can use the SHOW ENGINES<\/code> statement to list all available storage engines:<\/p>\n\n\n
SHOW ENGINES;<\/code><\/span><\/pre>\n\n\n
Output:<\/p>\n\n\n
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+\n| Engine             | Support | Comment                                                        | Transactions | XA   | Savepoints |\n+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+\n| MEMORY             | YES     | Hash based, stored in memory, useful for<\/span> temporary tables      | NO           | NO   | NO         |\n| MRG_MYISAM         | YES     | Collection of identical MyISAM tables                          | NO           | NO   | NO         |\n| CSV                | YES     | CSV storage engine                                             | NO           | NO   | NO         |\n| FEDERATED          | NO      | Federated MySQL storage engine                                 | NULL<\/span>         | NULL<\/span> | NULL<\/span>       |\n| PERFORMANCE_SCHEMA | YES     | Performance Schema                                             | NO           | NO   | NO         |\n| MyISAM             | YES     | MyISAM storage engine                                          | NO           | NO   | NO         |\n| InnoDB             | DEFAULT<\/span> | Supports transactions, row-level locking, and<\/span> foreign keys     | YES          | YES  | YES        |\n| ndbinfo            | NO      | MySQL Cluster system information storage engine                | NULL<\/span>         | NULL<\/span> | NULL<\/span>       |\n| BLACKHOLE          | YES     | \/dev\/null<\/span> storage engine (anything you write to it disappears) | NO           | NO   | NO         |\n| ARCHIVE            | YES     | Archive storage engine                                         | NO           | NO   | NO         |\n| ndbcluster         | NO      | Clustered, fault-tolerant tables                               | NULL<\/span>         | NULL<\/span> | NULL<\/span>       |\n+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+\n11<\/span> rows in set (0.00<\/span> sec)<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Note that MySQL 5.5 or later uses InnoDB as the default storage engine.<\/p>\n\n\n\n
To specify a storage engine when creating a new table, you use the ENGINE<\/code> clause in the CREATE TABLE<\/a> statement:<\/p>\n\n\n
CREATE<\/span> TABLE<\/span> table_name(\n    column_list\n) ENGINE<\/span> = engine_name;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
If you omit the ENGINE clause, MySQL will use the default storage engine for creating the table.<\/p>\n\n\n\n
MySQL storage engine features<\/h3>\n\n\n\n
The following table compares the features of the storage engine in MySQL:<\/p>\n\n\n\n
Feature<\/th>MyISAM<\/th>MEMORY <\/th>CSV<\/th>ARCHIVE<\/th>BLACKHOLE<\/th>MERGE<\/th>FEDERATED<\/th>InnoDB<\/th><\/tr>
Transactional<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
ACID Compliance<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
Table-level locking<\/td>Yes<\/td>No<\/td>Yes<\/td>Yes<\/td>Yes<\/td>No<\/td>Yes<\/td>Yes<\/td><\/tr>
Full-text search<\/td>Yes<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
Foreign key constraints<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
Crash recovery<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
External data access<\/td>No<\/td>No<\/td>Yes<\/td>Yes<\/td>No<\/td>No<\/td>Yes<\/td>No<\/td><\/tr>
Temporary tables<\/td>Yes<\/td>Yes<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr>
Default storage engine<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>No<\/td>Yes<\/td><\/tr><\/thead><\/table><\/figure>\n\n\n\n
InnoDB<\/h2>\n\n\n\n
The InnoDB<\/a> tables fully support ACID-compliant transactions<\/a>. They are also optimal for performance. InnoDB table supports foreign keys<\/a>, commit, rollback, and roll-forward operations. The size of an InnoDB table can be up to 64TB.<\/p>\n\n\n\n
Like MyISAM, the InnoDB tables are portable between different platforms and operating systems. MySQL also checks and repairs InnoDB tables, if necessary, at startup.<\/p>\n\n\n\n
MyISAM<\/h2>\n\n\n\n
The MyISAM<\/a> extends the former ISAM storage engine. The MyISAM tables are optimized for compression and speed. MyISAM tables are also portable between platforms and operating systems.<\/p>\n\n\n\n
The size of the MyISAM table can be up to 256TB, which is huge. In addition, MyISAM tables can be compressed into read-only tables to save space. At startup, MySQL checks MyISAM tables for corruption and even repairs them in case of errors. The drawback of the MyISAM tables is that they are not transaction-safe.<\/p>\n\n\n\n
Before version 5.5, MySQL used MyISAM as the default storage engine. From version 5.5, MySQL uses InnoDB as the default storage engine.<\/p>\n\n\n\n
MERGE<\/h2>\n\n\n\n
A MERGE<\/a> table is a virtual table that combines multiple MyISAM tables that have the same structure as one table. The MERGE storage engine is also known as the MRG_MyISAM<\/code> engine. The MERGE<\/code> tables do not have indexes. Instead, they use indexes of the component tables.<\/p>\n\n\n\n
If you use DROP TABLE<\/a><\/code> statement on a MERGE<\/code> table, MySQL removes only the MERGE<\/code> table and does not delete the underlying tables.<\/p>\n\n\n\n
The MERGE tables allow you to speed up performance when joining multiple tables<\/a>. MySQL only allows you to perform SELECT, DELETE, UPDATE, and INSERT<\/a> operations on the MERGE<\/code> tables. <\/p>\n\n\n\n
Memory<\/h2>\n\n\n\n
The MEMORY<\/a> tables store data entirely in memory and use hash indexes so that they are faster than MyISAM tables. <\/p>\n\n\n\n
The lifetime of the data of the MEMORY tables depends on the uptime of the database server. The memory storage engine was formerly known as HEAP.<\/p>\n\n\n\n
Archive<\/h2>\n\n\n\n
The ARCHIVE<\/a> storage engine allows you to store a large number of records for archiving purposes in a compressed format to save disk space. The ARCHIVE storage engine compresses a record when it is inserted and decompresses as it is read.<\/p>\n\n\n\n
The ARCHIVE tables only allow INSERT<\/a> and SELECT<\/a> statements. The ARCHIVE<\/code> tables do not support indexes, so it is required a full table scanning for reading rows.<\/p>\n\n\n\n
CSV<\/h2>\n\n\n\n
The CSV<\/a> storage engine stores data in comma-separated values (CSV) file format. A CSV table brings a convenient way to migrate data into non-SQL applications such as spreadsheet software.<\/p>\n\n\n\n
CSV table does not support NULL data type. In addition, the read operation requires a full table scan.<\/p>\n\n\n\n
BLACKHOLE<\/h2>\n\n\n\n
The BLACKHOLE<\/a> storage engine doesn’t store the table data. It means that the data that you send to a BLACKHOLE table is discarded. <\/p>\n\n\n\n
Therefore, The BLACKHOLE tables can be useful in a replication scenario where you want to capture data changes on the master server without storing that data on the local server.<\/p>\n\n\n\n
FEDERATED<\/h2>\n\n\n\n
The FEDERATED storage engine allows you to manage data from a remote MySQL server without using the cluster or replication technology. <\/p>\n\n\n\n
The local federated table stores no data. When you query data from a local federated table, the data is pulled automatically from the remote federated tables.<\/p>\n\n\n\n
Summary<\/h2>\n\n\n\n
    \n
  • A storage engine determines how MySQL stores, retrieves, and manipulates table data.<\/li>\n\n\n\n
  • MySQL uses InnoDB as the default storage engine.<\/li>\n\n\n\n
  • Use the ENGINE<\/code> clause in the CREATE STATEMENT<\/code> to explicitly instruct MySQL to use a specific storage engine other than the default storage engine.<\/li>\n\n\n\n
  • Each storage engine has it is own pros and cons, therefore choosing the right storage engine is critical for your application.<\/li>\n<\/ul>\n
    \n\t
    \n\t\t
    Was this tutorial helpful? <\/div>\n\t\t
    \n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t Yes <\/span>\n\t\t\t<\/button>\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t No <\/span>\n\t\t\t<\/button>\n\t\t<\/div>\n\t<\/header>\n\n\t
    \n\t\t
    \n\t\t\t
    <\/div>\n\t\t\t\n\t\t\t