5.4.1. Managing InnoDB Tablespaces

5.4.1.1. Enabling and Disabling File-Per-Table Mode
5.4.1.2. Specifying the Location of a Tablespace
5.4.1.3. Copying Tablespaces to Another Server (Transportable Tablespaces)
5.4.1.4. Moving the Undo Log out of the System Tablespace

Historically, all InnoDB tables and indexes were stored in the system tablespace. This monolithic approach was targeted at machines dedicated entirely to database processing, with carefully planned data growth, where any disk storage allocated to MySQL would never be needed for other purposes. InnoDB's file-per-table mode is a more flexible alternative, where you store each InnoDB table and its indexes in a separate file. Each such .ibd file represents a separate tablespace. This mode is controlled by the innodb_file_per_table configuration option, and is the default in MySQL 5.6.6 and higher.

Multiple tablespaces are useful in a number of situations:




Spec-Zone.ru - all specs in one place