Where can I obtain complete documentation for MySQL storage engines?
See note storage-engines::. That chapter contains information about all MySQL storage engines except for the note 'InnoDB': innodb-storage-engine. storage engine and the note 'NDB': mysql-cluster. storage engine (used for MySQL Cluster). note 'InnoDB': innodb-storage-engine. is covered in note innodb-storage-engine::. note 'NDB': mysql-cluster. is covered in *note mysql-cluster::.
Are there any new storage engines in MySQL 5.7?
No. 'InnoDB' is the default storage engine for new tables. See *note innodb-introduction:: for details.
Have any storage engines been removed in MySQL 5.7?
No.
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.
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 *note mysql-enterprise-backup::.
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 *note archive-storage-engine::, for details.
File: manual.info.tmp, Node: faqs-sql-modes, Next: faqs-stored-procs, Prev: faqs-storage-engines, Up: faqs