Operations | Monitoring | ITSM | DevOps | Cloud

This article examines DORA's requirements for database change management and explains how Redgate Flyway Enterprise addresses them. The EU's Digital Operational Resilience Act (DORA) came into full effect in January 2025. It is designed to strengthen the ability of financial institutions to withstand operational disruption, whether caused by technology failures, data corruption, human error, or a cyberattack.

Kellyn Gorman is a Database and AI Advocate and Engineer at Redgate She's the previous director of Data and AI at Silk, and the Oracle SME in Azure at Microsoft. With a robust background in cloud technology and a passion for promoting its merits and potential, I am thrilled to spearhead conversations and actions that help shape the future of this industry. Kellyn has authored numerous technical books, white papers and solution repositories in GitHub on database, AI and engineering topics.

It's 7am. An alert fired overnight. You open your monitoring solution, navigate to the alert, cross-reference the waits, check the query plans. Twenty minutes later: it should not have fired. You knew that before you started, but you had to check anyways. The feeling of being overwhelmed by alerts is real. And so is the cost. Thresholds set once and forgotten, firing on patterns that have been normal for months. The inbox fills. DBAs learn to ignore most alerts. The workaround becomes the workflow.

If anyone knows how to operate under scrutiny, it’s database teams within finance organizations. It’s a given considering the more rigorous compliance requirements and processes they must follow. But the 2026 State of the Database Landscape: Finance Edition reveals something more specific, and more uncomfortable, than the familiar story of regulatory pressure.

I'm happy to share some really exiting updates from the Flyway product teams this past month.

Every engineering team has a list of “things we don’t do”. No TRUNCATE TABLE in production. Every audit table must end in _audit. Foreign keys follow a naming convention. But until now, enforcing those standards has meant relying on pull request checklists, tribal knowledge, or a separate linting tool bolted onto the pipeline.

SQL Prompt's May releases focused on a new Redgate Data Modeler integration, a unified Toolbelt Essentials installer flow, and several improvements to Prompt AI reliability.