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,453 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

724 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,283 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,997 reads

Blogs

5 SQL Tricks Worth Remembering Before You Close the Laptop

By

Disclosure: this post may contain links to books as an affiliate link. If you...

Google – NotebookLM on ThakurVinay blog

By

Google has contributed a lot of stuff/enhancement on its portfolio, google is no longer...

Distance Metrics for Semantic Similarity Searches in SQL Server 2025

By

Next up in my series talking about The Burrito Bot is diving into the...

Read the latest Blogs

Forums

provisioning sql server via VMware Cloud Foundation

By andreas.kreuzberg

Hello, has anyone here ever provisioned and actually used an MS SQL Server with...

No More Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No More Deadlocks

Five SQL Server 2022 T-SQL Functions You Should Be Using Right Now

By vgupta

Comments posted to this topic are about the item Five SQL Server 2022 T-SQL...

Visit the forum

Question of the Day

No More Deadlocks

After detecting deadlocks in SQL Server 2025 and lowering the time threshold for detecting future issues, when does the Database Engine return to the 5s default interval?

See possible answers