msdb Is Too Big? Here’s What’s Actually Filling It
msdb is too big because backup history, job history, and mail logs pile up forever. See what’s filling it and how many days each source holds.
Database Health Monitor
Finding the Statement Inside a Loop in SQL Server
Spot the statement inside a loop running thousands of times inside a busy procedure, using Query Store data compared within its own module.
Is Your SQL Server Response Time Target Being Met?
Your SQL Server response time target means nothing until you can see what share of executions actually meet it, and which queries don’t.
Is a SQL Server Query Regression Statistically Significant?
See whether it is a SQL Server query regression statistically significant, or just noise from Query Store, before you tune anything.
Inside Database Health Monitor 4.1540: 63 New Reports, 25 Features and 515 Fixes
Database Health Monitor 4.1540 adds a 25 report Query Store suite, a 15 report SSRS suite, 23 new Azure SQL Health Monitor reports, 25 new features and 515 bug fixes. Here is what changed and why it matters.
Is This Query Slower Than Normal? Ask Its Own History
Is this query slower than normal? Learn how per-query limits from Query Store history separate a real slowdown from ordinary wobble.
master Backup Out of Date? Here’s How to Check It
A master backup out of date can pass every check and still miss logins, role grants, and linked servers created since it ran. Here’s how to see the gap.
SQL Server Job Slow When Others Run? Here’s Why
A job slow when others run isn’t a broken package. See how Database Health Monitor’s Subsystem Load report finds the Agent worker limit causing it.
Why Autogrowth in Percent Slows SQL Server Down
Autogrowth in percent compounds: every growth event takes longer than the last. Here’s how to spot it and fix it before it slows down SQL Server.
SQL Server Technical Debt: Where to Start Fixing It
SQL Server technical debt turns messy T-SQL into a weighted score and a cost estimate, so you know which procedure to fix first.