Detecting Data Masking Gaps in a CI Pipeline

If you use Redgate Test Data Manager to anonymize production-derived test data and Flyway to manage schema changes, you need a way to keep masking rules aligned with schema evolution. The most reliable approach is to validate masking coverage in CI: run a masking drift check as part of the Flyway pipeline and fail the build if schema changes introduce sensitive columns that aren’t yet covered by the masking configuration. This article shows how the check works, what it validates, and where it can fit into a typical delivery workflow. Read more

Safe Database Change at Scale with Flyway Enterprise

How do teams keep database change safe, controlled, and traceable as AI-assisted coding increases the pace of delivery? Redgate Flyway Enterprise builds the necessary controls, visibility, security checks, and traceability, directly into the database change process, so every change follows a controlled and verifiable path from commit to deployment. Read more

What’s under development in Redgate Flyway

In my recent posts, I looked back at the major features we shipped in 2025, highlighted all the exciting things going on in Flyway for Oracle databases, and shared the recent improvements to tracking dependencies for both SQL Server and Oracle databases. But that’s only part of the story. With four development teams working on Read more

Two Small Steps to Measurable Flyway Value

Flyway helps you regain control of complex legacy databases where even small changes can carry high risk. This article describes two small steps that deliver measurable improvements in control, code quality, and deployment reliability, without disrupting how the development team works. Read more

Simple Workflows for Flyway and Entity Framework Code First

Entity Framework Code First is great for development, but its abstractions can hide risky database changes until deployment. This article explores three practical EF–Flyway hybrid workflows that add visibility and control, helping teams stabilize deployments for complex, legacy databases such as monoliths. Read more

Color-coded Checks for your Current Flyway Environment

This article shows how to provide clearer feedback from the Flyway CLI by using environment-specific placeholders to provide details about the environment's purpose. It then illustrates how you might use this information to allow a scripted Flyway pipeline to give a simple code-coded message confirming the connected environment. Read more

Defining and Using Multiple Flyway Environments in TOML

This article shows how to define environments in your TOML files, use resolvers to provide secure connection details, and configure per-environment overrides and placeholders. It explains how this approach simplifies automation, makes CI/CD pipelines easier to manage, and helps teams work consistently and securely across multiple databases. Read more

Why Database Deployments Sometimes Go Bad

Phil Factor shares some of the common ways database deployments go wrong, and the testing strategies and sanity checks that will stop them happening to you. Read more

Managing Credentials Securely with Flyway Resolvers

One of the problems that creeps up on you as a Flyway project grows is how to manage securely the different credentials Flyway needs to access all the databases it needs to migrate. It's easy enough to get started by storing them in the TOML config files, but that approach isn't viable once you're dealing with sensitive data, multiple environments, or stricter security requirements. Fortunately, Flyway's Property Resolvers give us several ways to pull credentials, connection information and other config details from secure stores, such as secrets managers, at runtime. Read more

The Flyway Add Command Explained Simply

Flyway's add command creates an empty new migration file of the required type, ensuring use of the proper naming convention, assigning to it the correct version number, and placing it in the required location. This article explores how the command works and why it's especially useful when you want to add a new migration as part of an automated process. Read more