On this page
Drop the specified index on the specified table.
DROP INDEX <index_name> ON <table_name>;
<index_is the name of the index you want to drop.
<table_is the name of a table in a SingleStore database.
This command can be run on any SingleStore node (see Node Requirements for SingleStore Commands ).
This command will attempt to run as an online operation, but in certain cases cannot.
See ALTER TABLE for more information. Operations which must be run offline cannot be run on distributed tables.
SORT KEYindexes and
FULLTEXTindexes cannot be dropped using
If a table having these indexes is dropped, the indexes are deleted automatically.
KEY() USING CLUSTERED COLUMNSTOREis a legacy syntax that is equivalent to
SingleStore recommends using
SingleStore supports online
DROP INDEX, which means that you can read and write while the index is being dropped on a table.
DROP INDEXon a sharded table is always executed online.
Note that online
DROP INDEXwill not begin dropping the index on the table, but it will wait until all DML queries that were already running on the table finish.
This allows any in-progress queries to complete execution before dropping the index on the table, and ensures consistency of results from queries on the table since the time of execution of
As soon as the in-progress reads and writes complete and the
DROP INDEXcommand begins dropping the index on the table, new reads and writes will proceed as normal.
This blocking period usually lasts approximately for milliseconds.
If you are running frequent
DROP INDEXstatements on a table and have a lot of long-running queries on that table, then your normal workload may experience some periods of delay since it blocks other queries from starting while it waits for completion of long-running queries.
Refer to the Query Errors topic for resolving query timeout errors due to long running queries in a workload.
Refer to the Permission Matrix for the required permission.
DROP INDEX index_name ON table_name;
Last modified: April 4, 2023