Often, we want to test the new version of a database, produced by a Flyway migration, before committing the new migration file, or to test the same migration run on a number of different databases. This article demonstrates how to do it, by generating and using JSON parameter files to run a series of Flyway actions on any number of databases, on any number of servers.
2022-01-26
Flyway uses a schema history table to track the version of each database, recording in it every versioned migration file applied to build that version. It's worth understanding exactly how Flyway uses this table, the possible dangers of moving it to a non-default location and how to do it safely, if required.
2022-01-24
Phil Factor demonstrates some PowerShell tasks that will produce a high-level overview, or narrative, of the main differences in the metadata between two versions of a database, during Flyway Teams migrations.
2022-01-19
How to auto-generate first-cut undo scripts for every Flyway migration. For every new version of a database created by a Flyway versioned migration, we compare it to a 'source' directory containing object-level build scripts for the previous version. The SQL Compare engine does the rest, producing the associated undo script that will revert the database to the previous version, if required.
2022-01-12
Use Flyway to run your database migrations, each time automatically creating a SQL Change Automation release object to provide object-level scripts and a build script for the new version, along with change reports and code analysis reports.
2022-01-07
This article explains the fastest ways to restore the previous version of the database, to recover from a failed Flyway migration that leaves the database in an indeterminate state, and then how to adapt your database development process to avoid these problems.
2021-12-31
This article will get you up and running quickly with Flyway migrations on MariaDB or MySQL databases, from PowerShell.
2021-12-27
How to quickly and automatically bulk load test data once Flyway Teams completes a database migration. A baseline migration script creates the empty database version, which then triggers a PowerShell callback script that bulk loads in the right version of the data. It is a very fast way to provision multiple copies of a specific database version, complete with data, for ad-hoc or automated testing.
2021-12-24
How to add test data to a SQL Server database, during Flyway development. We use SQL Data Generator to produce some "realistic but fake" data and then SQL Data Compare to produce an INSERT script that Flyway can use to load the data into a newly-built version of the database.
2021-12-22
Demonstrates a cross-database PowerShell callback script for reporting on and auditing Flyway migrations, telling you which scripts were used to create each version, when they were run, who ran them and more.
2021-12-13
By ReviewMyDB
A behind-the-scenes look at Day of Data Jacksonville 2026, the transition from SQL Saturday,...
You run EXPLAIN ANALYZE on a slow query, stare at the plan, and something...
By Steve Jones
la guadière – n. a glint of goodness you notice in something that you...
hi, we couldnt get our upstream data source developers to supply what is sometimes...
Are there any good articles on all the trace flags that are enabled on...
Comments posted to this topic are about the item The Data Model Matters
I run the SQLCMD utility as follows:
lcmd -S localhost -EI then type this (the 1> is the prompt):
1> select @@version goIf I hit enter, what happens? See possible answers