Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 35.1Mb
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  / MySQL 5.7 Frequently Asked Questions  /  MySQL 5.7 FAQ: Storage Engines

A.2 MySQL 5.7 FAQ: Storage Engines

A.2.1. Where can I obtain complete documentation for MySQL storage engines?
A.2.2. Are there any new storage engines in MySQL 5.7?
A.2.3. Have any storage engines been removed in MySQL 5.7?
A.2.4. Can I prevent the use of a particular storage engine?
A.2.5. Is there an advantage to using the InnoDB storage engine exclusively, as opposed to a combination of InnoDB and non-InnoDB storage engines?
A.2.6. What are the unique benefits of the ARCHIVE storage engine?

A.2.1.

Where can I obtain complete documentation for MySQL storage engines?

SeeChapter 15,Alternative Storage Engines. That chapter contains information about all MySQL storage engines except for theInnoDB storage engine and theNDB storage engine (used for MySQL Cluster).InnoDB is covered inChapter 14,The InnoDB Storage Engine.NDB is covered inChapter 21,MySQL NDB Cluster 7.5 and NDB Cluster 7.6.

A.2.2.

Are there any new storage engines in MySQL 5.7?

No.InnoDB is the default storage engine for new tables. SeeSection 14.1, “Introduction to InnoDB” for details.

A.2.3.

Have any storage engines been removed in MySQL 5.7?

No.

A.2.4.

Can I prevent the use of a particular storage engine?

Yes. Thedisabled_storage_engines configuration option defines which storage engines cannot be used to create tables or tablespaces. By default,disabled_storage_engines is empty (no engines disabled), but it can be set to a comma-separated list of one or more engines.

A.2.5.

Is there an advantage to using theInnoDB storage engine exclusively, as opposed to a combination ofInnoDB and non-InnoDB storage engines?

Yes. UsingInnoDB tables exclusively can simplify backup and recovery operations. MySQL Enterprise Backup does ahot backup of all tables that use theInnoDB storage engine. For tables usingMyISAM or other non-InnoDB storage engines, it does a“warm” backup, where the database continues to run, but those tables cannot be modified while being backed up. SeeSection 28.1, “MySQL Enterprise Backup Overview”.

A.2.6.

What are the unique benefits of theARCHIVE storage engine?

TheARCHIVE storage engine stores large amounts of data without indexes; it has a small footprint, and performs selects using table scans. SeeSection 15.5, “The ARCHIVE Storage Engine”, for details.