Reference
Version · 6.0
Change Automation Reference

Maven futureRollbackSQL

Last updated: August 12, 2026

The futureRollbackSQL goal is a helper goal that produces the raw SQL Liquibase would need to roll back changes that have not yet been deployed to your database.

Uses

The futureRollbackSQL goal is typically used when you want to inspect the raw SQL that Liquibase would use to revert changes associated with undeployed changesets. The futureRollbackSQL goal generates the SQL that is required to roll back the database to the current state after the next update.

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

Note: The updateSQL goal is also a helper goal that you can use before running the update goal. The main difference is that updateSQL creates objects associated with undeployed changesets and futureRollbackSQL drops objects associated with undeployed changesets.

Maven configuration

You can configure Liquibase Maven in multiple ways. You can pass arguments like <changeLogFile> in Maven directly in your pom.xml file, in a liquibase.properties file referenced in your POM, as environment variables, or as JVM system properties. To learn about each file's syntax, see Maven Properties.

For more information about the Maven configuration, see Configuring Maven.

Before running the futureRollbackSQL goal, add <outputChangeLogFile>yourOutputFileName.txt</outputChangeLogFile> to pom.xml or set it in one of the other ways specified.

Running the futureRollbackSQL Maven goal

Running the futureRollbackSQL goal requires a Maven project to be implemented. To run the goal, type the following in your command prompt:

mvn liquibase:futureRollbackSQL

Attribute	Definition
`liquibase.changeLogDirectory`	Specifies the path to the directory where Liquibase can find your changelog file.
`liquibase.changeLogFile`	The changelog file for Liquibase to use.
`liquibase.changelogCatalogName`	Specifies the catalog Liquibase will use to create your changelog tables.
`liquibase.changelogSchemaName`	Specifies the schema Liquibase will use to create your changelog tables.
`liquibase.clearCheckSums`	Boolean. Forces checksums to be cleared from the DATABASECHANGELOG table. Default value is: false.
`liquibase.contexts`	Specifies which contexts Liquibase will execute, which can be separated by a comma if multiple contexts are required. If a context is not specified, then all contexts will be executed.
`liquibase.databaseChangeLogLockTableName`	Specifies the table name to use for the DATABASECHANGELOG table.
`liquibase.databaseChangeLogTableName`	Specifies the table name to use for the DATABASECHANGELOG table.
`liquibase.databaseClass`	Specifies the database object class.
`liquibase.defaultCatalogName`	Specifies the default catalog name to use for the database connection.
`liquibase.defaultSchemaName`	Specifies the default schema name to use for the database connection.
`liquibase.driver`	Specifies the driver class name to use for the database connection.
`driverPropertiesFile`	Specifies the location of a JDBC connection properties file which contains properties the driver will use.
`liquibase.emptyPassword`	Deprecated. Boolean. Use an empty or null value for the password instead. Default value is: false.
`expressionVariables`	Specifies a map-based collection of changelog properties to apply.
`expressionVars`	Specifies a property-based collection of changelog properties to apply.
`liquibase.includeArtifact`	Boolean. Includes a Maven project artifact in the class loader, which obtains the Liquibase properties file and changelog files. Default value is `true`.
`liquibase.includeTestOutputDirectory`	Boolean. Includes the Maven test output directory in the class loader which obtains the Liquibase properties file and changelog files. Default value is `true`.
`liquibase.labels`	Specifies which labels Liquibase runs, and which can be separated by a comma if multiple labels are required or you need to designate a more complex expression. If no label is specified, then all labels are run.
`liquibase.licenseKey`	Specifies your Liquibase Secure license key.
`liquibase.outputDefaultCatalog`	Boolean. Specifies whether to ignore the catalog or database name. Default value is: false.
`liquibase.outputDefaultSchema`	Boolean. Specifies whether to ignore the schema name. Default value is: false.
`liquibase.outputFileEncoding`	Indicates that you want to set the character encoding of the output file during the `updateSQL` phase.
`liquibase.password`	Specifies the database password for the database connection.
`liquibase.promptOnNonLocalDatabase`	Deprecated. Boolean. Controls whether users are prompted before executing changesets to a non-local database. Default value is: true.
`liquibase.propertyFile`	Specifies the Liquibase properties file to use for configuration, like `liquibase.properties`.
`liquibase.propertyFileWillOverride`	Boolean. Indicates that you want the `liquibase.properties` file to override any settings provided in the Maven plugin configuration. By default, if a property is explicitly specified, it is not overridden if it also appears in the properties file. Default value is: false.
`liquibase.propertyProviderClass`	Specifies the property provider, which must be a `java.util.Properties` implementation.
`liquibase.rollbackCount`	Defines the number of changesets to roll back. Default value is: 1.
`liquibase.rollbackDate`	Defines the date for which you want to roll back the database. The format of the date must match either an ISO date format or that of the `DateFormat.getDateInstance()` for the platform the plugin is being executed on.
`liquibase.rollbackTag`	Defines the tag for which you want to roll back the database.
`liquibase.server`	Specifies the server ID in the Maven `settings.xml` to use when authenticating.
`liquibase.skip`	Boolean. Specifies whether to skip running Liquibase. The use of this attribute is not recommended but can be used when needed. Default value is: false.
`systemProperties`	Specifies a list of system properties you want to pass to the database.
`liquibase.url`	Specifies the database URL you want to use to execute Liquibase.
`liquibase.username`	Specifies the database username for the database connection.
`liquibase.verbose`	Boolean. Controls the amount of output detail when you call the plugin. Default value is: false.

Maven futureRollbackSQL output

When successful, the futureRollbackSQL Maven goal produces the following output:

Starting Liquibase at 03:57:06 (version 4.1.1 #10 built at 2020-10-12 19:24+0000) [INFO] Char encoding not set! The created file will be system dependent! [INFO] Output File: C:\Users\Nataliya.WIN-20E107KB4TN\Desktop\Liquibase Projects\Maven Projects\my-liquibase-app\myfutureRollback.sql [INFO] Parsing Liquibase Properties File local.liquibase.properties for changeLog parameters [INFO] Executing on Database: jdbc:oracle:thin:@localhost:1521/ORCL [INFO] Successfully acquired change log lock [INFO] Reading from DATABASECHANGELOG [INFO] Successfully released change log lock [INFO] ------------------------------------------------------------------------ [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.341 s [INFO] Finished at: 2020-11-26T03:57:08-06:00 [INFO] ------------------------------------------------------------------------

Example of the output file

-- ********************************************************************* -- SQL to roll back currently unexecuted changes -- ********************************************************************* -- Change Log: dbchangelog.xml -- Ran at: 11/26/20 4:06 AM -- Against: MVN_UAT@jdbc:oracle:thin:@localhost:1521/ORCL -- Liquibase version: 4.1.1 -- ********************************************************************* -- Lock Database UPDATE DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = 'WIN-20E107KB4TN (172.30.3.88)', LOCKGRANTED = TO_TIMESTAMP('2020-11-26 04:06:50.763', 'YYYY-MM-DD HH24:MI:SS.FF') WHERE ID = 1 AND LOCKED = 0; -- Rolling Back ChangeSet: dbchangelog.xml::1606322157619-1::Nataliya (generated) DROP TABLE TEST; DELETE FROM DATABASECHANGELOG WHERE ID = '1606322157619-1' AND AUTHOR = 'Nataliya (generated)' AND FILENAME = 'dbchangelog.xml'; -- Release Database Lock UPDATE DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

PreviousMaven dropAll NextMaven generateChangeLog