- 14.2.1 Configuring InnoDB
- 14.2.2 InnoDB Startup Options and System Variables
- 14.2.3 Creating and Using InnoDB Tables
- 14.2.4 Changing the Number or Size of InnoDB Redo Log Files
- 14.2.5 Resizing the InnoDB System Tablespace
- 14.2.6 Backing Up and Recovering an InnoDB Database
- 14.2.7 Moving an InnoDB Database to Another Machine
- 14.2.8 The InnoDB Transaction Model and Locking
- 14.2.9 InnoDB Multi-Versioning
- 14.2.10 InnoDB Table and Index Structures
- 14.2.11 InnoDB Disk I/O and File Space Management
- 14.2.12 InnoDB Error Handling
- 14.2.13 InnoDB Troubleshooting
- 14.2.14 Limits on InnoDB Tables
InnoDB is a high-reliability and high-performance
storage engine for MySQL. Key advantages of
InnoDBtables arrange your data on disk to optimize common queries based on primary keys. Each
InnoDBtable has a primary key index called the clustered index that organizes the data to minimize I/O for primary key lookups.
To maintain data integrity,
FOREIGN KEYreferential-integrity constraints.
You can freely mix
InnoDBtables with tables from other MySQL storage engines, even within the same statement. For example, you can use a join operation to combine data from
MEMORYtables in a single query.
InnoDBhas been designed for CPU efficiency and maximum performance when processing large data volumes.
InnoDB storage engine maintains its own
buffer pool for caching data and indexes in main memory.
InnoDB stores its tables and indexes in a
tablespace, which may consist of several files (or raw disk
partitions). This is different from, for example,
MyISAM tables where each table is stored using
InnoDB tables can be very large
even on operating systems where file size is limited to 2GB.
The Windows Essentials installer makes
MySQL default storage engine on Windows, if the server being
The MySQL Enterprise Backup product lets you back up a running MySQL
MyISAM tables, with minimal disruption to
operations while producing a consistent snapshot of the database.
When MySQL Enterprise Backup is copying
tables, reads and writes to both
MyISAM tables can continue. During the copying of
MyISAM tables, reads (but not writes) to those
tables are permitted. In addition, MySQL Enterprise Backup supports
creating compressed backup files, and performing backups of subsets
InnoDB tables. In conjunction with MySQL’s
binary log, users can perform point-in-time recovery. MySQL
Enterprise Backup is commercially licensed. For a more complete
description of MySQL Enterprise Backup, see
Section 22.2, “MySQL Enterprise Backup Overview”.
A forum dedicated to the
InnoDB storage engine is
available at http://forums.mysql.com/list.php?22.
InnoDB is published under the same GNU GPL
License Version 2 (of June 1991) as MySQL. For more information on
MySQL licensing, see