Operations | Monitoring | ITSM | DevOps | Cloud

This is a guest post from James Hemson. Redgate Test Data Manager's latest release adds Entra ID authentication, multi-target anonymization, and direct treatment code editing, with workflow improvements to make pipeline management faster and more flexible. Entra ID Authentication You can now connect to SQL Server using token-based authentication via Azure Entra ID, for both anonymization and subsetting.

This is a guest post from Adrian Tan. Over recent months, we’ve been steadily improving PostgreSQL monitoring in Redgate Monitor, with a singular focus: to help Postgres users diagnose performance problems faster, with less manual investigation. The latest updates and new features tackle this problem in a few different ways.

SQL Prompt's February releases focused on compatibility and stability, with a critical fix for SSMS 22.3 users and several features graduating from experimental to fully supported.

This is a guest post from James Hemson. For years, the test data management market has told smaller companies the same story. Test data is complex. You need consultants. Compliance is expensive. Expect a six-month implementation before you see any value. At Redgate we think that's wrong. And we think it's wrong by design. Complexity creates services revenue. It creates switching costs. Most vendors have built their businesses around this.

This is a guest post from Nick Coombe. Redgate Monitor's built-in metrics cover the most common database pressure points out of the box. However, every estate has a few KPIs and metrics that are specific to the business, and users can create custom metrics to track those signals and receive an alert when they cross a threshold.

I recently wrote about a project I created on AWS Aurora PostgreSQL where I'm capturing APRS data from a radio. I focused on the ease of use, getting a database, some Lambda Functions, and a few schedulers working together with a web page. It was easy. However, I'd like to focus on a slightly different area now, performance.

When a database security incident happens, everyone turns to the security team. We look for a simple root cause analysis, and then we add a control, tighten a policy, and maybe even buy a silver bullet tool. We feel progress! But the incident didn’t start there. It started years earlier, when the organization made a series of perfectly reasonable decisions that quietly expanded the surface area and weakened the consistency of control.

This month’s highlights include smarter dependency handling in Flyway Desktop, and a look at how we’re starting the year strong for Oracle users. Plus: last call to share your feedback in our Flyway user survey (the prize draw closes soon!).

Deploying changes to Oracle databases can be complex from working across multiple schemas, handling dependencies, and accounting for environment differences. Flyway has been helping teams bring order and automation to Oracle development for over 15 years and in 2026 we’re accelerating that investment even further. Here’s a look at the latest enhancements available today and what’s coming next for Oracle users.

This is a guest post from Stephanie Herr. One of Flyway’s biggest strengths is its ability to track your database schema as individual SQL DDL scripts on disk. This gives you full version control over every object, along with a complete audit trail of what changed, who changed it, when it changed, and why. For teams working with Oracle and/or SQL Server, this level of transparency is essential and this latest release provides even more support for how you handle changes across dependent objects.