dropIndex

The dropIndex Change Type drops an existing index on a column.

Uses

You can typically use the dropIndex Change Type when you want to remove the specific index that identifies records in your database.

Once an index has been dropped, all metadata is removed. The index can’t be rebuilt and you must create it again. Also, if you drop a clustered index, the table will lose its identifiers.

Running the dropIndex Change Type

To drop an existing index in your database, follow these steps:

Step 1: Add the dropIndex Change Type to your changeset with the needed attributes as it is shown in the examples.

Step 2: Deploy your changeset by running the update command.

liquibase update

Available attributes

Name Description Required for Supports Since
catalogName The name of the catalog. all 3.0
indexName The name of the index to drop. all all
schemaName The name of the schema. all
tableName The name of the indexed table. asany, mariadb, mssql, mysql, sybase all 
<changeSet author="liquibase-docs" id="dropIndex-example">
    <dropIndex indexName="idx_address"
            schemaName="public"
            tableName="person"/>  
</changeSet>
changeSet:  
  id:  dropIndex-example 
  author:  liquibase-docs  
  changes: 
  -  dropIndex: 
      indexName:  idx_address  
      schemaName:  public  
      tableName:  person
{
  "databaseChangeLog":[
    {
      "changeSet":{
        "id":"dropIndex-example",
         "author":"liquibase-docs",
         "changes":[
           {
             "dropIndex":{
             "indexName":"idx_address",
             "schemaName":"public",
             "tableName":"person"
            }
          }
        ]
      }
    }
  ]
}
-- changeset DocUser:1:dropIndexChangeType
CREATE  UNIQUE  INDEX  idx_address  ON  department.person(address  DESC);

Database support

Database Notes Auto rollback
DB2/LUW Supported No
DB2/z Supported No
Derby Supported No
Firebird Supported No
H2 Supported No
HyperSQL Supported No
INGRES Supported No
Informix Supported No
MariaDB Supported No
MySQL Supported No
Oracle Supported No
PostgreSQL Supported No
SQL Server Supported No
SQLite Supported No
Sybase Supported No
Sybase Anywhere Supported No