Important
The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.
DROP TABLE
On this page
Drop the specified table.
Syntax
DROP [TEMPORARY] TABLE [IF EXISTS] <table_name> [FORCE];Remarks
-
<table_is the name of a table in a SingleStore database.name> -
This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).
-
This command causes implicit commits.
Refer to 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 TABLEcommand waits for the running queries to finish before dropping the table.To override this behavior and kill any running queries, use the FORCEoption. -
Table memory can be freed when the
DROP TABLEcommand is run.For information on when/how much table memory is freed when this command is run, see Managing Memory.
-
DROP TEMPORARY TABLEdoes not perform aCOMMITwhen run; issue aCOMMITprior toDROP TEMPORARY TABLEif 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 TABLEcommand, running theDROP TEMPORARY TABLEcommand does not commit implicitly. -
DROP TEMPORARY TABLEcannot drop global temporary tables. -
A temporary or global temporary table can be dropped using
DROP TABLEwithout specifying theTEMPORARYoption. -
Refer to the Permission Matrix for the required permissions.
Example
DROP TABLE IF EXISTS mytbl;
DROP TABLE IF EXISTS tab1 FORCE;
Last modified: July 20, 2023