This statement drops a tablespace that was previously created
CREATE TABLESPACE. It is
supported with all MySQL Cluster NDB 7.5 releases, and with
InnoDB in the standard MySQL Server as well,
beginning with MySQL 5.7.6.
ENGINE sets the storage engine that uses the
engine_name is the
name of the storage engine. Currently, the values
supported. If not set, the value of
default_storage_engine is used.
If it is not the same as the storage engine used to create the
DROP TABLESPACE statement
InnoDB tablespace, all tables must be
dropped from the tablespace prior to a
TABLESPACE operation. If the tablespace is not empty,
DROP TABLESPACE returns an error.
As with the
InnoDB system tablespace,
truncating or dropping
InnoDB tables stored in
a general tablespace creates free space in the tablespace
.ibd data file, which can
only be used for new
InnoDB data. Space is not
released back to the operating system by such operations as it is
for file-per-table tablespaces.
NDB tablespace to be dropped must not
contain any data files; in other words, before you can drop an
NDB tablespace, you must first drop each of its
data files using
... DROP DATAFILE.
Tablespaces are not deleted automatically. A tablespace must be dropped explicitly using
DROP DATABASEhas no effect in this regard, even if the operation drops all tables belonging to the tablespace.
DROP DATABASEoperation can drop tables that belong to a general tablespace but it cannot drop the tablespace, even if the operation drops all tables that belong to the tablespace. The tablespace must be dropped explicitly using
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.
This example demonstrates how to drop an
general tablespace. The general tablespace
is created with a single table. Before dropping the tablespace,
the table must be dropped.
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)->
ENGINE=INNODB;Query OK, 0 rows affected (0.02 sec) mysql>
DROP TABLE t1;Query OK, 0 rows affected (0.01 sec) mysql>
DROP TABLESPACE ts1;Query OK, 0 rows affected (0.01 sec)
This example shows how to drop an
myts having a data file named
mydata-1.dat after first creating the
tablespace, and assumes the existence of a log file group named
Section 14.1.15, “CREATE LOGFILE GROUP Syntax”).
CREATE TABLESPACE myts->
ADD DATAFILE 'mydata-1.dat'->
USE LOGFILE GROUP mylg->
You must remove all data files from the tablespace using
ALTER TABLESPACE, as shown here,
before it can be dropped:
ALTER TABLESPACE myts->
DROP DATAFILE 'mydata-1.dat'->
DROP TABLESPACE myts;