Flyway Database Migrations

Automate schema evolution for Snowflake, Redshift, SQL Server, and MySQL — version-controlled, pipeline-driven.

Best practice: create two pipeline steps — Flyway Info (view pending) followed by Flyway Migrate (deploy). This gives you a preview before committing changes.

Flyway Info Step (View Pending)

• Step Type: View pending migrations

• Flyway Database: Configured account from Tool Registry

• SCM Type: Bitbucket · GitLab · GitHubSCM Account / Workspace / Repo / Branch

• Source control details for the migration scripts

• Schema: Schemas managed by Flyway

• Base Schema: Hosts the Flyway schema history table

• Scripts Location: Location within SCM containing SQL scripts

• Database: Target database for migration

• Warehouse: Snowflake compute warehouse (hidden for Redshift/SQL Server/MySQL)Allow Out of OrderToggle to deploy migrations in any order

Flyway Migrate Step (Deploy Pending)

Same configuration as the Info step above, but set Step Type: Deploy pending migrations and choose the branch to migrate.

View Step Output

Pipeline → Summary → Pipeline Logs → click the Flyway step → Console Output. The Info step shows pending migrations; the Migrate step shows applied migrations and their status.