ALTER TABLESPACE Statement The  ADD DATAFILE  variant enables you to specify an initial size for an  NDB  Disk Data tablespace using an INITIAL_SIZE  clause, where  size  is measured in bytes; the default value is 134217728 (128 MB). You may optionally follow  size  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  (megabytes) or  G  (gigabytes). On 32-bit systems, the maximum supported value for  INITIAL_SIZE  is 4294967296 (4 GB). (Bug #29186) INITIAL_SIZE  is rounded, explicitly, as for  CREATE TABLESPACE . Once a data file has been created, its size cannot be changed; however, you can add more data files to an NDB tablespace using additional  ALTER TABLESPACE ... ADD DATAFILE  statements. When  ALTER TABLESPACE ... ADD DATAFILE  is used with  ENGINE = NDB , a data file is created on each Cluster data node, but only one row is generated in the  INFORMATION_SCHEMA.FILES  table. See the description of this table, as well as Section 23.5.10.1, “NDB Cluster Disk Data Objects” , for more information.  ADD DATAFILE  is not supported with  InnoDB  tablespaces. Using  DROP DATAFILE  with  ALTER TABLESPACE  drops the data file ’ file_name ’ from an NDB tablespace. You cannot drop a data file from a tablespace which is in use by any table; in other words, the data file must be empty (no extents used). See Section 23.5.10.1, “NDB Cluster Disk Data Objects” . In addition, any data file to be dropped must previously have been added to the tablespace with  CREATE TABLESPACE  or  ALTER TABLESPACE .  DROP DATAFILE  is not supported with  InnoDB  tablespaces. WAIT  is parsed but otherwise ignored. It is intended for future expansion. The  ENGINE  clause, which specifies the storage engine used by the tablespace, is deprecated; expect it to be removed in a future release. The tablespace storage engine is known by the data dictionary, making the ENGINE  clause obsolete. If the storage engine is specified, it must match the tablespace storage engine defined in the data dictionary. The only values for  engine_name  compatible with  NDB  tablespaces are  NDB and  NDBCLUSTER . RENAME TO  operations are implicitly performed in  autocommit  mode, regardless of the  autocommit setting. A  RENAME TO  operation cannot be performed while  LOCK TABLES  or  FLUSH TABLES WITH READ LOCK is in effect for tables that reside in the tablespace. Exclusive metadata locks are taken on tables that reside in a general tablespace while the tablespace is renamed, which prevents concurrent DDL. Concurrent DML is supported. The  CREATE TABLESPACE  privilege is required to rename an  InnoDB  general tablespace. The  AUTOEXTEND_SIZE  option defines the amount by which  InnoDB  extends the size of a tablespace when it becomes full. Introduced in MySQL 8.0.23. The setting must be a multiple of 4MB. The default setting is 0, which causes the tablespace to be extended according to the implicit default behavior. For more information, see Section 15.6.3.9, “Tablespace AUTOEXTEND_SIZE Configuration” . The  ENCRYPTION  clause enables or disables page-level data encryption for an  InnoDB  general tablespace or the  mysql  system tablespace. Encryption support for general tablespaces was introduced in MySQL 8.0.13. Encryption support for the  mysql  system tablespace was introduced in MySQL 8.0.16. A keyring plugin must be installed and configured before encryption can be enabled. As of MySQL 8.0.16, if the  table_encryption_privilege_check  variable is enabled, the TABLE_ENCRYPTION_ADMIN  privilege is required to alter a general tablespace with an  ENCRYPTION clause setting that differs from the  default_table_encryption  setting. 2506