Silent Job Failure: Read Missed Runs in This Order
A silent job failure writes no history and raises no alert. Here is the order to read the Missed Runs report so the gaps tell you what happened.
Database Health Monitor
SQL Server Plan Cache: Which Database Is Eating Memory?
Your SQL Server plan cache is memory that is not holding data pages. Split it by database, compare size to query count, and find the ad hoc SQL wasting it.
SQL Server CPU History: Read a Week in One Glance
Your SQL Server CPU history is a wall of spikes on a line chart. A heat map by hour and day shows the weekly pattern and the one day that broke it.
SQL Server Seek vs Scan: Why a Flat Read Count Lies
A flat read count can hide an index sliding from seeks to scans. Here is how the SQL Server seek vs scan ratio exposes it before queries slow down.
What’s New in Database Health Monitor 4.1626: Index Consolidation, Service Broker, Data Protection, Analysis Services and a Web Dashboard
Database Health Monitor 4.1626 adds an Index Consolidation Plan with a rollback script, reports for Service Broker, data protection and Analysis Services, and an opt-in read-only web dashboard.
msdb suspect_pages: Read the Date Before the Count
A walkthrough of the Suspect Pages report and the msdb suspect_pages table behind it: which column to read first, and how to spot a page still failing.
How Big Should master Be? What a Normal Size Is
How big should master be? A few megabytes is normal. Anything larger holds somebody’s data. See what the size means and what to check next.
Who Can See SSRS Reports? Check Broken Inheritance
Who can see SSRS reports on your server? Find the items that broke inheritance, the hidden Content Managers and the users who left, straight from the catalog.
Database Health Monitor 4.1625: 29 New Reports, 12 New Alerts and a Redesigned Performance Dashboard
Version 4.1625 adds 29 reports, 12 built-in alerts plus custom T-SQL alerts, a rebuilt performance dashboard, sensitive data discovery and 934 fixes. Here is the complete tour, report by report.
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.