Database Health Reports Beta 9 – Released

Today I have released beta 9 of the Database Health Monitor.

It has been 27 months since the release of Database Health Beta 1, and almost 4 years since the original SSRS implementation of Database Health reports.

To be honest for the first half of 2014, I didn’t contribute much to the Database Health Reports, then in the couple of months, I realized just how many people were really using Database Health Reports, with over 15oo active installs world wide. This changed my outlook on database health reports and I decided to buckle down and focus on the project again.


Beta 9 includes the following new features and bug fixes.

New Features

  • Added new real time report for Active Queries. This report shows the queries that are currently running (or blocked and waiting) on the current database. This was based on a customer request.
  • Right click menu option in the database tree view to sort the list of databases by either the database Id or alphabetically by name. This was based on a customer request.
  • New real time report to show database files with IO and stalls for database files and logs.

Bug Fixes

  • Improved the column formatting on the Identity Column Usage report. In some cases the columns were sized too small to read the column titles. This has been fixed.
  • Broken links have been fixed. There are a number of help links in the system that were linking to, these have been fixed to link to
  • Fixed crash caused by attempting to connect to a SQL Server that no longer exists.

With Beta 9 there has been more extensive testing with SQL Server 2014 to confirm that all the reports work correctly, so far there have been no problems with SQL server 2014.

Another infrastructure change with Beta 9 is that I migrated the source control system from Subversion and switched to Git. This has allowed for much easier branching and the addition of new code into the system.


If you are using Database Health Beta 8, I recommend you update to the latest free beta version at

Database Health Beta 8.2 has been released

For everyone using Database Health, sorry for the delay, other projects have been keeping me far to busy.

Today I released an update to Database Health called Beta 8.2. For those attempting to use Beta 8.1, please upgrade, and this should get you going again.

The download is available at:

Also this one never expires, so nobody should run into the timeout issue again.



Database Health Monitor – Beta 8 – Soft launch

Today I launched Database Health Reports Beta 8 as a soft launch. What I mean by the soft launch is that other than updating the DatabaseHealth website and this blog posting, I haven’t done much to promote it.  Why you might ask?  Due to it being a holiday week between Christmas and New Years, there are many people out of the office. I figured I would wait until after January 1st to make a big splash.

Beta 8 is out. The biggest change is the charting. About 75% of the charts in the system have been completely rewritten. I was using a charting module that didn’t allow for the flexiblity that was needed to make the charts look the way I wanted. In September right after the Beta 7 release I started rewriting the charts from scratch.  Between now and the next Beta I will work to get more of the charts converted over to the new look.

Here is an example of some of the newer charts. The red and green bars on the plan cache are used to indicate change.  Red indicates that the value was worse, and green indicates that it improved or stayed the same. The CPU by database chart was rewritten to make better use of the available space.

New Charts


Also shown in the above screen shot is the new Server Configuration panel with details on the specific version of SQL Server, when it was installed, the number of processors and more.

Beta 8 Release Notes

Beta 8 Released 12/29/2013.

The following changes have been made since Beta 7. The big feature in the Beta 8 is the rewrite of many of the charts.

New Features

  • Renamed to Database Health Monitor, attempting to avoid confusion with SSRS Reports.
  • Additional checks for obsolete or unusual settings (SHRINK_DATABASE, TORN_PAGE_DETECTION).
  • Blocking reporting with hierarchical drilldown on the blocking queries.
  • Server details panel showing logical and physical cpu counts, SQL Server Start time, SQL Server install data, Server Name, SQL Server version info, and information on real or virtual server.

Bug Fixes

  • Multithreading the re-connect of databases, vastly improving the startup time if one or more databases is not available.
  • A large amount of the project has been refactored to help mature the product and allow for additional feature growth, and reduce bugs.
  • Improved background threading.
  • Updates and bug fixes on SQL Technical Debt.

Beta 7++ Additional Cleanup on the Technical Debt

Again following the Agile philosophy of Release Early and Release Often, there is another minor release of Database Health Beta 7.  I called this one Beta 7++, the version has been updated to In this version the following minor features were added based on customer feedback and requests.

1. When filtering the Technical Debt by a specific type, which you can do by double clicking on the Debt By Type list, you can now un-filter, or clear the filter with the “Clear Filter and Show All” button.


2. When analyzing a single object for Technical Debt, when the analysis is complete, there is now a “Refresh” button displayed below the Analyze button to quickly re-analyze the same object. Also the Analysis Complete message has been extended to include the name of the object being analyzed.


3. Unrelated to technical debt but still worth mentioning is the reduced severity on the Huge Log Files warning.  Several people had asked for this, it is now less of a forbidding warning message.


That’s it for now. Please give Beta 7 Version 5.12 a try.

Have a great day!

-Steve Stedman

Beta 7+ Filter Technical Debt by Debt Type

One of the ideas behind Scrum software development is the idea of “Release early, Release Often and Get Customer Feedback.”

After the release of Beta 7 of the Database Health Reports earlier this week I received an email with a really great suggestion that I just had to implement.  The suggestion was to be able to click on the debt type and get the list of items with that debt.



If you are running Database Health Reports with a version (as shown in the title bar) less than and you want this new feature, just go to the download page and download the latest version.

Database Health Beta 7 Released – Featuring SQL Technical Debt Analysis

I have been working on Beta 7 over the last 3 months, and it is finally ready.  Beta 7  has been released today featuring the addition of the SQL Technical Debt reporting.  Besides the SQL Technical debt reporting, the other area of major improvement was the overall performance of the application.  There are many areas that previously were slow or difficult to work with that have been improved overall.

A quote from one of the early preview users is the following:

Excuse my language but that’s bloody amazing – it’s instant! Wow, good work :)
The entire application is so much more responsive, can’t believe it. The new colour is fantastic too, really changes the whole ‘quality’ feel of the application.

New Features

  • Technical Debt Reporting.
  • Support for SQL Server 2014 CTP1.
  • Full support for case sensitive databases. All features have been tested and confirmed good with case sensitive databases.
  • Historic Reporting Settings Dialog – Adding the ability to turn on or off monitoring for a specific database.
  • New Page Life Expectancy Tracking to the Historic Reports.
  • New CPU historic chart to the Historic Reports.
  • New “Create Script to Update All” Statistics button added to the Statistics report.

Bug Fixes

  • Multithreading the re-connect of databases, vastly improving the startup time if one or more databases is not available.
  • Speed improvements on every page in the application.
  • Improved speed on the Database Overview and Server Overview reports.
  • Re-factoring code – reducing technical debt.
  • Historic reporting – improved cleanup of historic data to keep the DBHealthHistory database from growing too large.
  • Fixed the settings dialog for the number of days to keep historic data.
  • Performance tuning clipboard copy from grids with many rows.
  • Performance improvements on the index fragmentation report.
  • Improved disconnect/reconnect when a database is no longer available, for instance a VPN connection was dropped or reconnected.
  • Fixing bugs with minimum page settings for the fragmented indexes report. It now displays the right data.

Here is a preview of the SQL Technical Debt Analysis:


Please give Beta 7 of Database Health a try, it may make your day more productive.


-Steve Stedman