future-rollback-count-sql

Last published July 28, 2025

The future-rollback-count-sql command generates the SQL that Liquibase would use to sequentially revert the number of changes associated with undeployed changesets, which are added to a changelog file.

Uses

The future-rollback-count-sql command is typically used to inspect the SQL before rolling back the number of changesets you have not deployed to your database, but added to your changelog. The command shows the output starting with the most recent changes until the value specified is reached.

It is best practice to inspect SQL, which Liquibase would run when using the rollback command, so you can review any changes the command would make to your database.

Syntax

To run the future-rollback-count-sql command, specify the driver, classpath, and URL in the Liquibase properties file. You can also specify these properties in your command line.

Then run the future-rollback-count-sql command:

liquibase future-rollback-count-sql --count=2 --changelog-file=example-changelog.xml

Note: The --count=myCount syntax was added in Liquibase 4.4. If you use an older version, specify your count as a positional argument: <command> myCount.

Note: The username and password attributes are not required for connections and systems that use alternate means of authentication. Also, you can specify database credentials as part of the url attribute.

Command parameters

Global parameters

Attribute

Definition

Requirement

--output-file=<string>

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

Optional

Command parameters

Attribute

Definition

Requirement

--changelog-file=<string>

The root changelog

Required

--count=<int>

An integer specifying how many changes Liquibase applies the command to. Specify as --count=myCount. Positional format <command> <count> deprecated in 4.4+.

Required

--url=<string>

The JDBC database connection URL.

Required

--context-filter=<string>

Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run.

Note: If you use Liquibase 4.23.0 or earlier, use the syntax --contexts instead of --context-filter.

Optional

--default-catalog-name=<string>

Name of the default catalog to use for the database connection

Optional

--default-schema-name=<string>

Name of the default schema to use for the database connection. If defaultSchemaName is set, then objects do not have to be fully qualified. This means you can refer to just mytable instead of myschema.mytable.

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

Optional

--driver=<string>

The JDBC driver class

Optional

--driver-properties-file=<string>

The JDBC driver properties file

Optional

--label-filter=<string>

Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.

Optional

--output-default-catalog=<true|false>

Control whether names of objects in the default catalog are fully qualified or not. If true, they are. If false, only objects outside the default catalog are fully qualified. Default: true.

Optional

--output-default-schema=<true|false>

Control whether names of objects in the default schema are fully qualified or not. If true, they are. If false, only objects outside the default schema are fully qualified. Default: true.

Optional

--password=<string>

Password to connect to the target database.

Tip: It is best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.

Optional

--username=<string>

Username to connect to the target database.

Tip: It is best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.

Optional

Output

When successful, the future-rollback-count-sql command produces the following output:

-- ********************************************************************* -- SQL to roll back currently unexecuted changes -- ********************************************************************* -- Change Log: dbchangelog.xml -- Ran at: 3/11/21 1:02 PM -- Against: SCHEMA1@jdbc:oracle:thin:@localhost:1521:ORCL -- Liquibase version: 4.1.1 -- ********************************************************************* -- Lock Database UPDATE SCHEMA1.DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = 'WIN-20E107KB4TN (172.30.3.88)', LOCKGRANTED = TO_TIMESTAMP('2021-03-11 13:02:26.103', 'YYYY-MM-DD HH24:MI:SS.FF') WHERE ID = 1 AND LOCKED = 0; -- Rolling Back ChangeSet: dbchangelog.xml::89::liquibase DROP TABLE SCHEMA1.table34558223; DELETE FROM SCHEMA1.DATABASECHANGELOG WHERE ID = '89' AND AUTHOR = 'liquibase' AND FILENAME = 'dbchangelog.xml'; -- Rolling Back ChangeSet: dbchangelog.xml::88::liquibase DROP TABLE SCHEMA1.table3455822;