CREATE TABLESPACE Statement A general tablespace is a shared tablespace. It can hold multiple tables, and supports all table row formats. General tablespaces can be created in a location relative to or independent of the data directory. After creating an  InnoDB  general tablespace, use  CREATE TABLE  tbl_name  ... TABLESPACE [=] tablespace_name  or  ALTER TABLE  tbl_name  TABLESPACE [=]  tablespace_name  to add tables to the tablespace. For more information, see Section 15.6.3.3, “General Tablespaces” . Undo tablespaces contain undo logs. Undo tablespaces can be created in a chosen location by specifying a fully qualified data file path. For more information, see Section 15.6.3.4, “Undo Tablespaces” . This statement is used to create a tablespace, which can contain one or more data files, providing storage space for NDB Cluster Disk Data tables (see Section 23.5.10, “NDB Cluster Disk Data Tables” ). One data file is created and added to the tablespace using this statement. Additional data files may be added to the tablespace by using the  ALTER TABLESPACE  statement (see Section 13.1.10, “ALTER TABLESPACE Statement” ). All NDB Cluster Disk Data objects share the same namespace. This means that each Disk Data object  must be uniquely named (and not merely each Disk Data object of a given type). For example, you cannot have a tablespace and a log file group with the same name, or a tablespace and a data file with the same name. A log file group of one or more  UNDO  log files must be assigned to the tablespace to be created with the USE LOGFILE GROUP  clause.  logfile_group  must be an existing log file group created with  CREATE LOGFILE GROUP  (see Section 13.1.16, “CREATE LOGFILE GROUP Statement” ). Multiple tablespaces may use the same log file group for  UNDO  logging. When setting  EXTENT_SIZE  or  INITIAL_SIZE , you may optionally follow the number with a one-letter abbreviation for an order of magnitude, similar to those used in  my.cnf . Generally, this is one of the letters M  (for megabytes) or  G  (for gigabytes). INITIAL_SIZE  and  EXTENT_SIZE  are subject to rounding as follows: NDB  reserves 4% of a tablespace for data node restart operations. This reserved space cannot be used for data storage. The rounding just described is done explicitly, and a warning is issued by the MySQL Server when any such rounding is performed. The rounded values are also used by the NDB kernel for calculating INFORMATION_SCHEMA.FILES  column values and other purposes. However, to avoid an unexpected result, we suggest that you always use whole multiples of 32K in specifying these options. When  CREATE TABLESPACE  is used with  ENGINE [=] NDB , a tablespace and associated data file are created on each Cluster data node. You can verify that the data files were created and obtain information about them by querying the  INFORMATION_SCHEMA.FILES  table. (See the example later in this section.) (See Section 26.3.15, “The INFORMATION_SCHEMA FILES Table” .) 2598 Note Note Considerations for NDB Cluster • EXTENT_SIZE  is rounded up to the nearest whole multiple of 32K. • INITIAL_SIZE  is rounded  down  to the nearest whole multiple of 32K; this result is rounded up to the nearest whole multiple of  EXTENT_SIZE  (after any rounding).