renameSequence

Last updated: March 26, 2026

Last updated: March 25, 2026

Renames an existing sequence.

Known issue: The Liquibase renameSequence change type is not compatible for Snowflake users in Liquibase Secure 5.1 using YAML or JSON change type formats. This does not affect XML change types at all. If you’re connecting to a Snowflake database, Liquibase automatically detects you are using the Snowflake renameSequence change type and breaks backwards compatibility with the Liquibase renameSequence change type. We recommend upgrading to Liquibase Secure 5.1.1 to use createView with YAML and JSON change type formats successfully.

Run renameSequence

To run this Change Type, follow these steps:

  1. Add the Change Type to your changeset, as shown in the examples on this page.

  2. Specify any required attributes. Use the table on this page to see which ones your database requires.

  3. Deploy your changeset by running the update command:liquibase update

Available attributes

Name

Description

Required for

Supports

Since

catalogName

Name of the catalog

all

3.0

newSequenceName

New name for the sequence

all

all

oldSequenceName

Existing name of the sequence to rename

all

all

schemaName

Name of the schema

all

Database support

Database

Notes

Auto Rollback

DB2/LUW

Not Supported

No

DB2/z

Not Supported

No

Derby

Not Supported

No

Firebird

Not Supported

No

Google BigQuery

Supported

No

H2

Not Supported

No

HyperSQL

Not Supported

No

INGRES

Not Supported

No

Informix

Not Supported

No

MariaDB

Not Supported

No

MySQL

Not Supported

No

Oracle

Supported

Yes

PostgreSQL

Supported

Yes

Snowflake

Supported

Yes

SQL Server

Supported

Yes

SQLite

Not Supported

No

Sybase

Not Supported

No

Sybase Anywhere

Supported

Yes

renameSequence examples

loading

loading

loading

loading