Operations | Monitoring | ITSM | DevOps | Cloud

The AI said I had to do a database first, not code. Who am I to argue? So, with all the prompts outlining the goals of the project, I’ve gone forward with the project, and step one is creating a PostgreSQL database on Azure. This is part three of a multi-part set of articles. I’ll move this list to the bottom of future articles: Part 1: Introducing the Concept of dbRosetta Part 2: Defining the Project & Prompt Templates.

Whether it’s a stalled Log Reader Agent, a conflicting insert on the subscriber, or a failed cleanup job bloating the distribution database, Redgate Monitor now brings SQL Server replication issues to light early, before performance or reliability are affected. In many SQL Server environments, replication remains essential for offloading reporting and analytics workloads, or for maintaining local and synchronized data copies across regions.

This is the next installment of the series on building a database and an application called dbRosetta using AI/LLM. Part 1 introduces the concept. THE AI PICKED DATABASE FIRST! Look, I talk databases at this thing a lot, so it probably knows my own preference, but when I asked it, it chose to build a database separate from the code. Let’s get into it.

SQL Prompt’s November release brings new features to SQL Prompt AI, bug and performance fixes to SQL History and support for SQL Server 2025 preview.

Like many of you, over the last couple of years, I’ve been using AI, or, well, let’s just name it appropriately, Large Language Models (LLM), as a part of my job. I’ve also used it in my hobby. With it, I’ve generated snippets of code, tested data conversions, even built a small database for a presentation. However, to date, I haven’t tried doing everything through the LLM. Now, I’m going to.

Redgate Monitor now surfaces two common SQL Server query issues that usually take manual work to uncover: cancelled or aborted queries and high memory-grant queries. You can now see both in the Query Executions view for each SQL Server instance, directly alongside server activity and alerts, so you can diagnose the cause much faster. Recently, Redgate Monitor introduced the Query Executions feature for SQL Server instances, using Extended Events to capture execution details for individual queries.

Redgate Test Data Manager’s November’s release brings advanced table configuration for large databases and the ability to save connection strings. Two features that make setting up subsets and managing database connections smoother, easier, and faster.

With increasing security threats and stringent compliance requirements, database code quality isn’t just a best practice; it’s a business imperative. Yet many organizations struggle to enforce their database development standards consistently across teams, leading to security vulnerabilities, potential data loss, and lengthy review cycles that slow down software delivery.