This month is a big one! We announced the latest major release of Redgate Flyway Enterprise, built to help teams move fast with AI without losing control of the database. Three key new capabilities also landed in preview: Flyway’s MCP server, advanced support for Databricks, and Oracle schema existence checks. And we're closing with a short, honest read on failure and what it takes to make deployments less stressful. Here's the round-up.

A database change control layer for enterprises scaling AI

AI is changing how quickly software gets built, and the database is where a lot of that speed runs into risk. The latest major release of Redgate Flyway Enterprise is designed to close that gap, so teams can embrace AI-generated code and agentic workflows while keeping database change governed, validated, and auditable.

At the center of the release is the new Flyway Enterprise MCP Server, which brings a governed, agentic approach to managing database change. Every AI-driven change is captured, validated, and auditable. The full launch announcement including the future direction for Flyway Enterprise is here: Redgate introduces database change control layer to support enterprises scaling AI.

Advanced capabilities for Databricks, now in preview

The advanced capabilities that SQL Server, Oracle, and PostgreSQL teams already rely on in Flyway Enterprise are now available for Databricks. Features for managing Lakehouse objects via Unity Catalog integration are in preview, and we can support you on the journey to Databricks Lakebase for your OLTP and AI workloads too. That means versioning every schema change, generating versioned and undo migration scripts, catching problems before they ship, and detecting drift, all across your whole data platform.

The full write-up is here: Announcing Redgate Flyway Enterprise's advanced capabilities for Databricks now in preview.

We're also working on advanced support for Snowflake and Microsoft Fabric, extending the same governed approach across more of the analytics estate. If that's of interest to your team, email us. We'd love to hear from you.

Oracle schema existence checks, now in preview

When generating versioned and undo migration scripts for Oracle projects, you can now include object existence checks in the generated SQL. Because Oracle auto-commits DDL, a migration that fails partway through can leave a partially applied state that's fiddly to clean up by hand. With existence checks, each DDL statement is wrapped in a conditional, so if you need to re-run the script, objects that already exist are skipped rather than throwing errors, and recovery from a timeout becomes a simple flyway repair then flyway migrate. Full details: Oracle schema existence checks are now in preview in Flyway Enterprise.

One more read: to learn and improve, we can't be afraid to fail

A lot of this month's news is about making fast, AI-driven change safe, but tooling is only half the story. In this piece, software craftsman Rob Richardson argues that deployment stress often starts when a fear of failure seeps into a team's culture: the build goes red and the first question is "Who's to blame?" His fix is a learning mindset over a blame-first one, digging into root causes and making the machine do more after every failure. A good reminder that safer deployments come from the workflow and the way we treat mistakes. Read it here: To learn and improve, we cannot be afraid to fail.

Feedback

As always, we'd love to hear what you think of these updates. Email us with any comments or questions, or book a 30-minute Zoom call with the development team.