DROP TABLE

<table_name> is the name of a table in a SingleStore database.

This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStoreDB Commands ).

This command causes implicit commits. See COMMIT for more information.

If there is a view which depends on a table, the table cannot be dropped. See CREATE VIEW for more information.

By default, the DROP TABLE command waits for the running queries to finish before dropping the table. To override this behavior and kill any running queries, use the FORCE option.

Table memory can be freed when the DROP TABLE command is run.

For information on when/how much table memory is freed when this command is run, see Managing Memory.

DROP TEMPORARY TABLE does not perform a COMMIT when run; issue a COMMIT prior to DROP TEMPORARY TABLE if there are uncommited statements.

Because temporary tables only exist for the duration of a client session, no access privileges are required to run DROP TEMPORARY TABLE.

Unlike when running the DROP TABLE command, running the DROP TEMPORARY TABLE command does not commit implicitly.

DROP TEMPORARY TABLE cannot drop global temporary tables.

A temporary or global temporary table can be dropped using DROP TABLE without specifying the TEMPORARY option.

See the Permission Matrix for the required permission.