Learn how to use Flyway for Automated Database Migrations
A learning path for managing and automating database deployments, from version control, using Flyway.
You’ll need to click on the image once to open it, and then the links in each article box will work.
Key:
- Yellow box = Flyway Community Edition
- Blue box = Requires Flyway Teams Edition
- Red box = Requires Flyway Enterprise
For further information about Flyway:
- Flyway documentation
- Flyway video training courses on Redgate University
Tools in this post
You may also like
-
Article
Dealing with Cross-Server Database Dependencies in Flyway Projects
How to tackle database development in Flyway when databases make cross-server references. The technique uses synonyms to represent the remote objects, and local 'stub' objects to overcome the problems caused by 'missing references' when building the individual objects.
-
Article
Flyway How-tos: a User's Perspective
Flyway provides a database-independent way for a team to track, manage and apply database changes, while maintaining strict control of database versions. It updates a database by running a series of versioned migration scripts, in order, and keeps track of all the changes in a special "schema history" table. It sounds simple, but it is easy to derail this team discipline if you don't find the right answers to the following questions…
-
Article
Creating Idempotent DDL Scripts for Database Migrations
How to write idempotent DDL scripts that Flyway can run several times on a database, such as after a hotfix has already been applied directly to the production database, without causing errors.
-
Article
Automating Flyway Development Chores using Database Diagrams
If you can produce a quick Entity-Relationship diagram for any version of a database, you'll have a simple way to 'sanity check' it for unreferenced tables, missing keys and other design flaws. This article shows how to auto-generate these diagrams when running a migration, using Flyway Teams and PowerShell.
-
Article
Why and how you should automate database migrations
The desire to release features faster and deliver value to customers sooner is prompting many IT teams to adopt DevOps and Agile practices. By automating parts of the development process where possible and working in shorter cycles to release small changes more often, those teams that do well experience fewer errors and produce higher quality code.
-
