Pre-General Availability Draft: 2017-05-29
tablespace_nameADD DATAFILE '
file_name' [FILE_BLOCK_SIZE = value] [ENGINE [=]
This statement is used to create an
InnoDB tablespace created using
CREATE TABLESPACE is referred to as
A general tablespace is a shared tablespace, similar to the system tablespace. It can hold multiple tables, and supports all table row formats. General tablespaces can also be created in a location relative to or independent of the MySQL data directory.
After creating an
InnoDB general tablespace,
you can use
tbl_name ... TABLESPACE [=]
to add tables
to the tablespace.
tbl_name TABLESPACE [=]
For more information, see Section 16.7.9, “InnoDB General Tablespaces”.
CREATE TABLESPACE is supported with
InnoDB. In earlier releases,
TABLESPACE only supported
NDB, which is the MySQL NDB Cluster
ADD DATAFILE: Defines the name of the tablespace data file. A data file must be specified with the
CREATE TABLESPACEstatement, and the data file name must have a
InnoDBgeneral tablespace only supports a single data file.
To place the data file in a location outside of the MySQL data directory (
DATADIR), include an absolute directory path or a path relative to the MySQL data directory. If you do not specify a path, the general tablespace is created in the MySQL data directory.
To avoid conflicts with implicitly created file-per-table tablespaces, creating a general tablespace in a subdirectory under the MySQL data directory is not supported. Also, when creating a general tablespace outside of the MySQL data directory, the directory must exist prior to creating the tablespace.
, including the path (optional), must be quoted with single or double quotations marks. File names (not counting the “.ibd” extension) and directory names must be at least one byte in length. Zero length file names and directory names are not supported.
FILE_BLOCK_SIZE: Defines the block size of the tablespace data file. If you do not specify this option,
FILE_BLOCK_SIZEsetting is only required if you will use the tablespace to store compressed
ROW_FORMAT=COMPRESSED). In this case, you must define the tablespace
FILE_BLOCK_SIZEwhen creating the tablespace.
innodb_page_size, the tablespace can only contain tables with an uncompressed row format (
DYNAMICrow formats). Tables with a
COMPRESSEDrow format have a different physical page size than uncompressed tables. Therefore, compressed tables cannot coexist in the same tablespace as uncompressed tables.
For a general tablespace to contain compressed tables,
FILE_BLOCK_SIZEmust be specified, and the
FILE_BLOCK_SIZEvalue must be a valid compressed page size in relation to the
innodb_page_sizevalue. Also, the physical page size of the compressed table (
KEY_BLOCK_SIZE) must be equal to
FILE_BLOCK_SIZE/1024. For example, if
KEY_BLOCK_SIZEof the table must be 8. For more information, see Section 16.7.9, “InnoDB General Tablespaces”.
ENGINE: Defines the storage engine which uses the tablespace, where
engine_nameis the name of the storage engine. Currently, only the
InnoDBstorage engine is supported.
ENGINE = InnoDBmust be defined as part of the
CREATE TABLESPACEstatement or
InnoDBmust be defined as the default storage engine (
is a case-sensitive identifier for the tablespace. It may be quoted or unquoted. The forward slash character (“/”) is not permitted. Names beginning with
innodb_are either not permitted or are reserved for special use.
Creation of temporary general tablespaces is not supported.
General tablespaces do not support temporary tables.
TABLESPACEoption may be used with
ALTER TABLEto assign
InnoDBtable partitions or subpartitions to a general tablespace, a separate file-per-table tablespace, or the system tablespace. All partitions must belong to the same storage engine. For more information, see Section 16.7.9, “InnoDB General Tablespaces”.
innodb_strict_modeis not applicable to general tablespaces. Tablespace management rules are strictly enforced independently of
CREATE TABLESPACEparameters are incorrect or incompatible, the operation fails regardless of the
innodb_strict_modesetting. When a table is added to a general tablespace using
CREATE TABLE ... TABLESPACEor
ALTER TABLE ... TABLESPACE,
innodb_strict_modeis ignored but the statement is evaluated as if
DROP TABLESPACEto remove a general tablespace. All tables must be dropped from a general tablespace using
DROP TABLEprior to dropping the tablespace.
All parts of a table added to a general tablespace reside in the general tablespace, including indexes and
Similar to the system tablespace, truncating or dropping tables stored in a general tablespace creates free space internally in the general tablespace .ibd data file which can only be used for new
InnoDBdata. Space is not released back to the operating system as it is for file-per-table tablespaces.
A general tablespace is not associated with any database or schema.
The server uses tablespace-level metadata locking for DDL that references general tablespaces. By comparison, the server uses table-level metadata locking for DDL that references file-per-table tablespaces.
A generated or existing tablespace cannot be changed to a general tablespace.
There is no conflict between general tablespace names and file-per-table tablespace names. The “/” character, which is present in file-per-table tablespace names, is not permitted in general tablespace names.
This example demonstrates creating a general tablespace and adding three uncompressed tables of different row formats.
mysql> CREATE TABLESPACE `ts1` ADD DATAFILE 'ts1.ibd' Engine=InnoDB; Query OK, 0 rows affected (0.01 sec) mysql> CREATE TABLE t1 (c1 INT PRIMARY KEY) TABLESPACE ts1 ROW_FORMAT=REDUNDANT; Query OK, 0 rows affected (0.00 sec) mysql> CREATE TABLE t2 (c1 INT PRIMARY KEY) TABLESPACE ts1 ROW_FORMAT=COMPACT; Query OK, 0 rows affected (0.00 sec) mysql> CREATE TABLE t3 (c1 INT PRIMARY KEY) TABLESPACE ts1 ROW_FORMAT=DYNAMIC; Query OK, 0 rows affected (0.00 sec)
This example demonstrates creating a general tablespace and adding
a compressed table. The example assumes a default
innodb_page_size of 16K. The
FILE_BLOCK_SIZE of 8192 requires that the
compressed table have a
KEY_BLOCK_SIZE of 8.
mysql> CREATE TABLESPACE `ts2` ADD DATAFILE 'ts2.ibd' FILE_BLOCK_SIZE = 8192 Engine=InnoDB; Query OK, 0 rows affected (0.01 sec) mysql> CREATE TABLE t4 (c1 INT PRIMARY KEY) TABLESPACE ts2 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8; Query OK, 0 rows affected (0.00 sec)