• Reference
  • Version · 6.0
  • Change Automation Reference

Snowflake alterSequence

Last updated: September 29, 2026

Modifies properties of an existing sequence in Snowflake. This allows you to change the increment value and ordering behavior without recreating the sequence.

Note: This change type does not support automatic rollback.

Available attributes

Attribute

Type

Description

Required

catalogName

String

Name of the catalog (database) containing the sequence

No

schemaName

String

Name of the schema containing the sequence

No

sequenceName

String

Name of the sequence to alter

Yes

ifExists

Boolean

Don't error if the sequence doesn't exist using IF EXISTS

No

incrementBy

Long

New value to increment by for each sequence value*

No

ordered

Boolean

New ordering behavior (true for ORDER, false for NOORDER)*

No

* At least one of incrementBy or ordered must be specified.

Snapshot and diff support

As of Liquibase Secure 6.0, diff detects differences in the ordered property of a Snowflake sequence, and diff-changelog generates a corrective pro-snowflake:alterSequence changeset. When incrementBy and ordered both differ, Liquibase combines them into a single changeset, because Snowflake sets both in one ALTER SEQUENCE statement.

Note: Snowflake does not allow changing a sequence from NOORDER to ORDER. When diff finds that difference, Liquibase logs a warning and generates no changeset. Drop and recreate the sequence to enable ORDER. The reverse direction, ORDER to NOORDER, generates a changeset normally.

Two further differences do not produce a changeset:

  • A comment difference generates a separate pro-snowflake:alterSequenceComment changeset instead of pro-snowflake:alterSequence.

  • A difference in startValue, minValue, or maxValue is reported in the log only. Snowflake requires you to drop and recreate the sequence to change these, so diff-changelog does not generate a changeset for them.

loading

loading

loading

loading