alterSequence

Last updated: March 26, 2026

Last updated: March 25, 2026

Alters properties of an existing sequence.

Known issue: The Liquibase alterSequence 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 that you are using the Snowflake alterSequence change type and breaks backwards compatibility with the Liquibase alterSequence change type. We recommend upgrading to Liquibase Secure 5.1.1 to use createView with YAML and JSON change type formats successfully.

Run alterSequence

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

cacheSize

Number of values to fetch per query

asany, db2, db2z, derby, h2, hsqldb, informix, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase

catalogName

Name of the catalog

asany, db2, db2z, derby, h2, hsqldb, informix, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase

cycle

Boolean. Can the sequence cycle when it hits the max value?

asany, db2, db2z, derby, h2, hsqldb, informix, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase

dataType

Data type of the sequence

asany, derby, informix, postgresql

incrementBy

Integer amount to increment by at each call

asany, db2, db2z, derby, informix, mssql, oracle, postgresql

maxValue

Sets the maximum value of the sequence

asany, db2, db2z, derby, h2, informix, mssql, oracle, postgresql

minValue

Sets the minimum value of the sequence

asany, db2, db2z, derby, h2, hsqldb, informix, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase

ordered

Boolean. Does the sequence need to be guaranteed to be generated in the order of request?

asany, db2z, derby, h2, informix, oracle, postgresql

schemaName

Name of the schema

asany, db2, db2z, derby, h2, hsqldb, informix, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase

sequenceName

Name of the sequence

all

all

Database support

Database

Notes

Auto Rollback

DB2/LUW

Supported

No

DB2/z

Supported

No

Derby

Supported

No

Firebird

Supported

No

Google BigQuery

Supported

No

H2

Supported

No

HyperSQL

Supported

No

INGRES

Not Supported

No

Informix

Supported

No

MariaDB

Not Supported

No

MySQL

Not Supported

No

Oracle

Supported

No

PostgreSQL

Supported

No

Snowflake

Supported

No

SQL Server

Supported

No

SQLite

Not Supported

No

Sybase

Not Supported

No

Sybase Anywhere

Supported

No

alterSequence examples

loading

loading

loading

loading