MySQL :: MySQL 8.4 Reference Manual :: A.2 MySQL 8.4 FAQ: Storage Engines

version 8.4

8.0 current
5.7

8.0 Japanese

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

A.2 MySQL 8.4 常见问题解答：存储引擎

A.2.1. Where can I obtain complete documentation for MySQL storage engines?
A.2.2. Are there any new storage engines in MySQL 8.4?
A.2.3. Have any storage engines been removed in MySQL 8.4?
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?
	See Chapter 18, Alternative Storage Engines. That chapter contains information about all MySQL storage engines except for the `InnoDB` storage engine and the `NDB` storage engine (used for MySQL Cluster). `InnoDB` is covered in Chapter 17, The InnoDB Storage Engine. `NDB` is covered in Chapter 25, MySQL NDB Cluster 8.4.
A.2.2.	Are there any new storage engines in MySQL 8.4?
	No. `InnoDB` is the default storage engine for new tables. See Section 17.1, “Introduction to InnoDB” for details.
A.2.3.	Have any storage engines been removed in MySQL 8.4?
	No.
A.2.4.	Can I prevent the use of a particular storage engine?
	Yes. The `disabled_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 the `InnoDB` storage engine exclusively, as opposed to a combination of `InnoDB` and non-`InnoDB` storage engines?
	Yes. Using `InnoDB` tables exclusively can simplify backup and recovery operations. MySQL Enterprise Backup does a hot backup of all tables that use the `InnoDB` storage engine. For tables using `MyISAM` 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. See Section 32.1, “MySQL Enterprise Backup Overview”.
A.2.6.	What are the unique benefits of the `ARCHIVE` storage engine?
	The `ARCHIVE` storage engine stores large amounts of data without indexes; it has a small footprint, and performs selects using table scans. See Section 18.5, “The ARCHIVE Storage Engine”, for details.

PREV HOME UP NEXT