How to find the query that ran at 3 a.m. after the fact. It uses nothing but what SQL Server 2025 keeps on its own. I planted a culprit, gave it eight disguises and buried it in four hundred innocent lookups. Then I tracked it down with Query Store. This is the poster.
Slow Queries: A Field Guide to Eight Species
Slow queries, identified the way a field guide identifies birds: by silhouette, habitat, call, and the species they’re confused with. All eight were raised in the lab on SQL Server 2025. The reads and the wait types are what each one produced.
Outdated Statistics in SQL Server: The Optimizer Is Planning for Last Year
Outdated statistics in SQL Server can slow a query even when its code has not changed. On SQL Server 2025 with the legacy estimator, a stale statistic sent one join to 120,043 logical reads, and a targeted update brought it down to 18,220. Auto update helps, but it waits for a threshold, it samples, and it knows nothing about the rows that arrived today.
SQL SERVER – Execution Plans and Indexing Strategies – Quick Guide
Let us learn today in this quick guide Execution Plans and Indexing Strategies. Your comments are welcome
SQL SERVER – Catching Non-SARGable Queries in Action
If you ever wondered why a query that looks harmless is performing poorly despite having indexes in place, the answer could non-SARGable queries.
SQL SERVER Performance Tuning: Catching Key Lookup in Action
In this blog post, we’ll explore what a Key Lookup is, how to spot it, and most importantly, how to eliminate it using a covering index.
Majoring in the Minors in SQL Server Performance Tuning
We’ll explore how to avoid this common pitfall & Focus the areas that matter for performance improvements. Avoid majoring in the minors.