Operations | Monitoring | ITSM | DevOps | Cloud

You open a stored procedure to make what should be a quick fix, and something doesn't add up. There's a filter you don't recognize, or a column that has changed type, or a join that looks like it was added in a hurry. Who changed this? When? And, most importantly, why? We're excited to announce that object level history is now available for Redgate Flyway Enterprise users of Flyway Desktop.

G2's Fall 2026 Grid Report for Database Monitoring is out, and Redgate Monitor is named a Leader. G2 builds its reports from verified user reviews rather than paid placement, so this recognition comes from the people who use Redgate Monitor every day, and took time out of their lives to tell others what it's like. So, a big thank you to our customers, we're grateful for every review.

Assessing the cost of a database monitoring tool isn't always straightforward. The quick reaction is to solely assess costs on a license-for-license basis.

Snowflake has become a core part of how many teams store, model, and analyze their data. As more of the business comes to depend on Snowflake, the schema needs the same governance and control as any other production system. Too often, schema change in Snowflake happens through ad hoc scripts, tribal knowledge, or direct access in Snowsight.

"Why do I need to give Flyway this extra database?" That's one of the most common blockers we hear from users setting up a Flyway project. Flyway has long had a concept of a build database or shadow database that is a dedicated sandbox database for Flyway to do background work in. It's required for Flyway to be able to simulate what running a set of migrations will do to a database.

How much of your database delivery can you actually see? For most teams, the picture is scattered. Deployment status lives in CI logs and scripts. Drift appears outside the process. And with AI multiplying the volume and speed of changes moving through pipelines, the risk that comes with low visibility rises with every release.

Redgate Monitor now closes that gap. You can monitor reader nodes for the first time, alongside the writer node support we already had, and get a cluster-wide view that ties node-level health back to overall cluster performance.

Every organization knows what their database monitoring tool costs on the invoice. Almost none of them have added up what it costs in the people running it, the incidents it doesn't catch fast enough, and the savings sitting in the environment that nobody has visibility to find.

The Digital Operational Resilience Act (DORA) has applied to financial organizations across the EU since January 2025 and is designed to strengthen their ability to withstand operational disruption. What the roundtables revealed was that although these financial organizations had completed extensive DORA planning exercises, this groundwork was not reliably translating into auditable operational control.

AI coding assistants have changed how fast application code gets written. Copilot, Cursor, Claude Code, and agentic tools built on top of them can generate a working feature in minutes. But none of them know your database's history. They don't know that a migration already renamed that column last sprint, that a policy forbids unqualified DELETE statements, or that the target environment has drifted from what your migrations say it should look like.