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 9.5.
|
A.2.2. |
Are there any new storage engines in MySQL 9.5?
|
|
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 9.5?
|
|
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.
|