Signal waits are the part of every wait that a task spends in the queue for a free CPU. This post ranks the wait types by signal time, shows why timer waits ruin the total share, and samples the signal share into a small table so a whole working day can be read interval by interval.
THREADPOOL Waits: When Raising Max Worker Count Helps
THREADPOOL waits mean tasks waited for a worker thread. Five read-only queries separate real thread starvation from blocking and busy CPUs. The post lists five signs and shows how to raise the cap in small steps.
Filtered Statistics: Fixing Estimates for Skewed Data
Use filtered statistics to describe skewed customer values, inspect histograms, and test estimates under literal and parameterized queries.
SQL SERVER – Query Specific Wait Statistics and Performance Tuning
Query Specific Wait Statistics helped explain a sudden customer-query slowdown. The remaining workload ran normally, and recompilation had not helped.
Unique Index Performance: What a UNIQUE Index Saves
Unique index performance gains come from what the optimizer learns, not from smaller pages. A tested demo compares pages, reads, plans and CPU for a plain index and a unique index. It also shows the error a duplicate causes.
DBCC DROPCLEANBUFFERS Impact on Memory: See a Cold Cache in Action
DBCC DROPCLEANBUFFERS removes every clean page from memory, so the next query reads from disk. This post counts the pages of one database before and after, shows why a CHECKPOINT comes first, and compares a cold read with a warm read.
CHECKPOINT Impact on Memory: Watch Dirty Pages Go to Zero
CHECKPOINT impact on memory is easy to measure. This post counts the dirty and clean pages of one database before and after a checkpoint. Dirty pages drop to zero, the clean pages grow by the same amount, and nothing leaves memory.







