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.
2021-05-21
How to extend the range of SQL code analysis, during database development, to include dynamic analysis of the database metadata. This will allow regular checks for problems with the design of your tables and indexes ("table smells") that can affect database performance and data integrity.
2021-05-10
A set of PowerShell automation script tasks for running database build and migrations tasks. This article describes the SQL code analysis task, which will check the syntax of the SQL code in your databases and your migration scripts for 'code smells'.
2021-04-30
How to detect database drift prior to running a database migration, so that you can be certain that a database hasn't been subject to any 'uncontrolled' changes that could affect the migration or result in untested changes being deployed to production.
2021-04-28
This article provides PowerShell automation scripts for running Flyway database migrations. These scripts use SQL Compare to automatically generate all the required database build artifacts in the version control system, for each Flyway deployment.
2021-04-26
How to create a batch file that executes any number of database migration tasks across a range of servers and databases, using Flyway.
2021-04-21
Describing the two main use cases for occasional "cherry picking" of Flyway database migration scripts: back-filling emergency production hotfixes to version control and managing parallel development streams.
2021-04-05
During development you need a fast, automated way to build multiple copies of a database on any development or test server, with each database at the right version. This article provides a PowerShell automation script for Flyway that will do the job.
2021-04-02
How to send Flyway logging and error output to JSON and consume it in PowerShell to produce ad-hoc database migrations reports, including any errors that occurred, the version of the database, runtimes for each migration script and more.
2021-04-01
There are certain checks that need to be done after a database migration is complete. One good example of this is the check that a migration script, such as one that merges changes from a branch into main, doesn't cause 'invalid objects' (a.k.a. 'missing references') in your databases. I'll show you how to run this check, using sp_RefreshSQLModule, and incorporate it into a Flyway "after" migration script.
2021-03-25
By Steve Jones
Thanks to everyone for attending my session on running a Local LLM. If you...
By Steve Jones
I do believe that Redgate has been very customer focused since it’s inception. I’ve...
By James Serra
There’s a question I’ve been hearing more and more lately, especially as Copilot, Fabric,...
Hi everyone I am getting below warning when I run SSIS: Warning: 0x80049304 at...
Comments posted to this topic are about the item Let's Talk Community Events!
Hi as shown below a replication target requires a primary key. if we want...
By default, how often is the SQL Server Database Engine checking for deadlocks?
See possible answers