The data professional’s world is changing and I know you hear this from me in editorials, blogs posts and social media, but it’s the truth. With the rise of Microsoft Fabric, we’re not just seeing another platform shift; we’re witnessing a redefinition of how data is valued, governed, and protected across the enterprise. Fabric isn’t […]
Introduction It was the week before Black Friday — the biggest online ad rush of the year. Our US-based ad-tech platform was gearing up for an insane traffic spike. Hundreds of real-time campaigns were about to go live across multiple brands, each with thousands of user sessions flowing through our system. Every incoming user impression […]
Take a basic look at database diagrams, what they are, and how to create one.
Unlocking Interoperability: A Guide to Foreign Data Wrappers in PostgreSQL and Aurora PostgreSQL AWS RDS As a database professional, I often encounter scenarios where data is fragmented across various systems. In today's distributed IT landscape, it's not uncommon for critical business information to reside in different databases, perhaps an on-premise PostgreSQL instance for legacy applications, […]
As with others, I've had to deal with death in the family recently. Some other family members are dealing with cancer (a few friends too). Happily none of us has recently been a disaster zone, but that's happened too. So yeah, big, nasty scary stuff happens in life. However, for most of us, most of […]
I was just reading about how the Philippines are working to update their databases in support of faster and better responses in the case of an emergency. While I do volunteer for some of the local emergency services, I'm right at the bottom of the heap as just a radio operator. I don't have any […]
In this article, I wanted to test a common assumption we DBAs make – that adding INCLUDE columns to indexes is harmless. I created a FULL recovery test database with a realistic wide Orders table containing extra large VARCHAR columns to simulate an ERP workload. I ran updates and measured transaction log backup sizes before and after adding INCLUDE columns to a nonclustered index. The results shocked me. The update without INCLUDE columns generated a 10 MB log backup, while the same update with INCLUDE columns produced over 170 MB – a 17x increase in log volume. I explain why this happens: INCLUDE columns are physically stored in index leaf rows, so updates affecting them write bigger log records. I also clarify that updating key columns generates even more log than INCLUDE updates because it involves row movement (delete + insert), but INCLUDE updates still cost more log than if those columns weren’t indexed at all. The takeaway is clear – INCLUDE columns are powerful, but they silently increase transaction log generation, impacting backup sizes, replication lag, and DR readiness. Always measure their real cost before deploying to production.
In Part 1, I explored how to bend SQL Server Agent to our will and peek under the hood of Azure SQL Managed Instance (SQL MI), gaining full OS access to the container (all without relying on xp_cmdshell). But once I realized what kind of door I'd opened, curiosity pushed us further, tempting us to […]
In this next article, we look at creating balanced dimensions on demand.
By Chris Yates
In today’s enterprise landscape, agility and reliability go hand-in-hand. As organizations modernize legacy infrastructure...
By Steve Jones
I’m honored to be speaking at the PASS Data Community Summit in Seattle this...
By Brian Kelley
herefore, from Northwind and pubs to WideWorldImporters, I've compiled where to get those databases...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item We Gave Memory-Optimized Tables a...
Comments posted to this topic are about the item Always On AG Latency for...
You're responsible for managing a SQL Server environment using Always On Availability Groups across two data centers. During a recent planned failover to the secondary replica, you noticed increased application latency and errors related to read-only routing. Upon investigation, you discover that read-only routing continues pointing to the former primary, now a secondary, for a period of time after the failover.
Which of the following best explains this behavior and how to resolve it?