Using the available provisioners, you can provision a database which does not exist yet before connecting to it, or reprovision the shadow database, restoring the database back to a known state.

Flyway Desktop currently supports Redgate Clone provisioning and Docker provisioning via the UI. They can be selected using the dropdown in the database connection dialog. The clean provisioner is used under the hood as the default behaviour for the shadow database.

These are available in Preview.  If you are trying to use this feature or have feedback about this feature, please get in touch with our Database DevOps Development Team.

Docker - Preview

EDITION: ENTERPRISE

This provisioner automatically provisions a database in a Docker container with minimal configuration. It detects the database engine and version to use, selects a matching Docker image, and spins up a container using raw Docker commands. This makes it ideal for quickly standing up a build environment - for example in a CI pipeline - with little or no configuration.

The engine and version can be detected automatically from the target environment, probed from another sourceEnvironment, or set explicitly with databaseEngine  and databaseEngineVersion .

By default the container is kept alive between Flyway invocations so subsequent commands can reuse it.

Prerequisites:

• Docker must be installed and available on the machine running Flyway

Some database engines (SQL Server and Oracle) require you to accept the vendor's EULA before a container can be provisioned, which is done by setting iAgreeToTheDBVendorsEula  to true .

For the full list of configuration options and examples see here.