SQLServerCentral Article

We Gave Memory-Optimized Tables a Hash Lookup — Then Tried Pattern Matching Instead

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 […]

(6)

You rated this post out of 5. Change rating

2025-07-22

2,424 reads

SQLServerCentral Article

When INCLUDE Columns Quietly Inflate Your Transaction Logs

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.

(3)

You rated this post out of 5. Change rating

2025-07-18

713 reads

SQLServerCentral Article

Unmasking CXPACKET and CXCONSUMER in SQL Server: What Your Execution Plan Isn’t Telling You

This article dives deep into cxpacket and cxconsumer in sql server, explaining how to simulate each, when they appear, and why they matter. Using live execution plans, wait monitoring, and worker thread diagnostics, we uncover how uneven parallelism triggers thread sync waits—and how SQL Server sometimes hides real issues behind innocent-looking CXCONSUMER waits. Includes step-by-step queries, tuning tips, and a real-world scenario where repartition streams quietly ruined performance.

(5)

You rated this post out of 5. Change rating

2025-07-07

4,051 reads

SQLServerCentral Article

How to Safely Remove a SQL Server Data File Without Downtime

Learn how to safely remove a SQL Server .ndf data file without any downtime using DBCC SHRINKFILE (EMPTYFILE). This hands-on tutorial walks through real-world Azure-based setup, data redistribution, and storage cleanup — ideal for DBAs managing enterprise SQL Server environments.

(3)

You rated this post out of 5. Change rating

2025-05-16

2,782 reads

Blogs

The DIY Cost of Masking Test Data For Smaller Organizations

By

One of the things I’ve tried hard to do in database development situations if...

T-SQL Tuesday #196 – Two risky career decisions I made

By

The T-SQL Tuesday topic this month comes James Serra. What career risks have you...

T-SQL Tuesday #192: What career risks have you taken?

By

This T-SQL Tuesday is hosted by the one and only James Serra – literally...

Read the latest Blogs

Forums

XACT_ABORT being set to ON by web services

By zoggling

We have two "identical" instances of an ASP.NET web service (or so I have...

OPENQUERY Flexibility

By Steve Jones - SSC Editor

Comments posted to this topic are about the item OPENQUERY Flexibility

A Full Shutdown

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Full Shutdown

Visit the forum

Question of the Day

OPENQUERY Flexibility

Which of these are valid OPENQUERY() uses?

See possible answers