Every year around audit and compliance season, support tickets start arriving with the same urgent theme: DBAs need a fully automated, completely hands-off way to produce the same comprehensive SQL Server health reports they normally generate manually inside the Database Health Monitor GUI — but without ever having to open the application.
They wanted to schedule a task that runs at 3 AM (or 7 AM, or every four hours) would wake up, connect to one or many instances, collect every piece of diagnostic data the GUI shows, and drop a finished, professional-looking report into a shared folder or email it — all with zero clicks and zero pop-ups. That real-world demand is exactly why we built true silent mode and the new command-line parameters in Database Health Monitor.
With the latest release, Database Health Monitor can now run 100% from the command line or scheduled task and produce the exact same rich reports you see in the interactive application:
- Full deadlock history with complete deadlock graphs
- Current and historical blocking chains
- CPU, memory, and wait-stats trends
- Backup status and history for every database
- Database and file-growth trends
- Index fragmentation and usage statistics
- Missing indexes and query store insights
- Configuration checks and best-practice alerts
- And dozens of additional health checks
The new parameters make automation simple and flexible. You specify the report type (Quick Scan, Full Health Report, History Report, etc.), the output folder, the file format (HTML or PDF), and the target instance name. The tool automatically pulls saved connection details (server name, authentication, encryption settings) from the existing configuration files, so a single command can generate reports for 5, 10, or 50 instances in sequence without storing passwords in plain text or batch files.
Many teams now have a scheduled task that runs at 7:00 AM every weekday. By the time the DBA opens their inbox or checks the network share, a fresh, timestamped report is already waiting — giving them an instant snapshot of blocking, deadlocks, backup failures, space trends, and performance counters from the moment the server woke up. Historical reports stay in dated folders, so comparing today’s report against last week or last month becomes trivial, and long-term trends jump off the page.
This entire capability exists because actual customers told us — often in all-caps emails during crunch time — that they needed it. Database Health Monitor has always been driven by the real day-to-day pain points of SQL Server professionals, and this silent/automated reporting feature is one of the clearest examples yet.
If you have ever wished you could get the full power of Database Health Monitor without touching the GUI, try the new command-line options today. And please keep the feedback and feature requests coming — the next improvement is almost certainly something another DBA just like you is asking for right now.