About

Every administrator starts collecting scripts or procedures on how to accomplish their tasks. After asking himself “Where did that script go?” Steve Stedman (twitter @sqlEmt) decided to put all his knowledge into an application and the Database Health Tool was created.  Since 2010, Steve has been working on this tool as he can to help both our customers and those how need a visual way to look at how their SQL Servers are performing.

Knowing the status of all your SQL Servers

One of the common issues administrators face is the inability to get a monitoring tool to help collect metrics and as a result, there can be real performance issues in the lower environments.  The Database Health Monitor changes all of that.  The monitor can be used on all your SQL Servers to get a better sense of what is going on with every SQL Server instance so you don’t have to guess or make assumptions about your environments.

• September 2024 – Version 1072 of Database Health Monitor. 2 new developers working on this release. See release notes for over 15 new features. Several bug fixes.
• July 2024 – Version 1067 of Database Health Monitor. Added tracking of database sizes over time. Several bug fixes.
• February 2024 – Version 1055 of Database Health Monitor. Added upgrade recommendations report. Expanded on the TempDB reports, and what is active reports. Several bug fixes.
• February 2024 – Version 1052 of Database Health Monitor. New columns on the IO reports. Dynamic resizing of instance reports. New TempDB high usage report. Several bug fixes.
• January 2024 Version 1039 of Database Health Monitor. Added new TempDB use by hour to the historic reporting. Several bug fixes.
• December 2023 Version 1034 of Database Health Monitor. Refactored some of the agent jobs on the historic reporting. Several bug fixes.
• November 2023 – version 1028 of Database Health Monitor. Added resource and resource info intothe what is active report. Added check #211 to the quickscan report. More work on the dark mode. Several bug fixes.
• October 2023 Version 1024 of Database Health Monitor. Updated the background error reporting to include more details on the specific error location on background thread crashes. This will allow our team to do more with tracking crash reports. QuickScan added slow error log acess, and check for differential backups missing. Several bug fixes.
• August 2023 Version 1022 of Database Health Monitor. Added to QuickScan, and added ability to clean up orphaned users.
• June 2023 – Version 1018 of Database Health Monitor. Big performance improvements for when 20+ servers are connected, or with fewer if slower connections.
• May 2023 – Version 1015 of Database Health Monitor. Quickscan and Performance Monitor improvements.
• April 2023 – Version 1008 and 1009 of Database Health Monitor. Bug fixes and new features.
• January 2023 – Version 1007 of Database Health Monitor. Bug fixes and new features.
• November 2022 – Version 1005 release of Database Health Monitor. Big improvements on the security check report based on the latest industry standards for locking down a SQL Server.
• August 2022 – Version 1002. Mostly bug fixes, and improving some report draw issues.
• July 2022 – Version 999. Big performance improvements on the Historic Wait Monitoring reporting. New report I/O by hour for each database.
• January 2022 – Version 991 release of Database Health Monitor. Many feature updates and bug fixes. Introducing the new gamification for connection points.
• June 2021 – Version 982 release of Database Health Monitor. Several updates including the updated SQL Performance Monitor.
• January 2021 – Version 977 release of Database Health Monitor. Lots of performance improvements in this version.
• September 2020 – Version 972 release of Database Health Monitor. Added checks to the Quick Scan Report along with several bug fixes.
• December 2019 – Version 2.9.5 release of Database Health Monitor.
• November 2019 – Version 2.9.4 release of Database Health Monitor.
• October 2019 – Version 2.9.2 release of Database Health Monitor.
• September 2019 – Version 2.9.1 release of Database Health Monitor. Several new features including aliasing for servers, or a way to add a tag name to the server as it is displayed in the list view. Useful for associating machine names with IP addresses. Requested by a customer.
• August 2019 – Version 2.9 release of Database Health Monitor. Added a new Blocking Heat Map report that shows by day and by hour when blocking is occurring.
• July 2019 – Version 2.8.2 release of Database Health Monitor.
• June 2019 – Version 2.8.1 release of Database Health Monitor.
• March 2019 – Version 2.7 release of Database Health Monitor.
• November 12, 2018 – Version 2.6.6 released. Several updates to the Quick Scan report, and a couple of minor bug fixes.
• September 2018 – Version 2.6.5 released. Modifications to the historic waits and additional Quick Scan report checks.
• August 2018 – Version 2.6.4 released.  Adding version checks for SQL Server 2017, Quick Scan improvements, and bug fixes.
• October 28, 2017 – Version 2.6.1 released. New reports added.
• October 21, 2017 – Version 2.6 released. Several bugs fixed an reports added for job history.
• June 5, 2017 – Version 2.5.5 released. Enhanced several existing reports.
• May 9, 2017 – Version 2.5.4 released. Added new reports that scan across all SQL Server instances connected to.
• March 13, 2017 – Version 2.5.3. Blocking query report moved to the instance level.
• February 19, 2017 – Version 2.5 released. New features.
• January 2, 2017 – Version 2.4.5 released. New logos, icons and branding, plus several fixes.
• October 3, 2016 – Version 2.4.4 released.
• June 1, 2016 – Version 2.4 Released. New reports, new features and several bug fixes.
• March 20, 2016 – Version 2.3 Released.
• December 5, 2015 – Version 2.2 Released.
• July 3, 2015 – Version 2.0 Released.
• June 1, 2015 – Beta 10.2 Released. Improved performance on historic reporting. Allows for multiple connections to different reporting database. Automatically detects if a server is already configured for historic reporting.
• May 6, 2015 – Beta 10.1 Released. Removed the crowd funding, and added a couple new reports, the Error Log Report and the Suspect Pages Report. Many bug fixes.
• January 21, 2105 – Beta 10 Released.  New icon, crow funding links, added filegroup and partitioning key into the partitioning report. Many bug fixes.
• December 21, 2014 – Beta 9.4 Release, improved overall threading and background processing.
• December 14, 2014 – Beta 9.3 Release, more bug fixes and more new Partitioned tables reports.
• December 7, 2014 – Beta 9.2 Release, more bug fixes and more new reports.
• November 30, 2014 – Beta 9.1 Release, more bug fixes and more new reports.
• November 23, 2014 – Beta 9 Release, bug fixes and a couple of new reports.
• October 5, 2014 – Beta 8.2 Release.
• January 19, 2014 – Beta 8.1 Release – bug fixing.
• December 29th, 2013 – Beta 8 Release – most of the charts rewritten, eliminating extra components.
• Sept 5th, 2013 – Second Release of Beta 7 with a new feature to filter technical debt by debt type.
• Sept 2nd, 2013 – Release of Beta 7 including SQL Technical Debt Analysis, and many performance improvements.
• July- August 2013 – Working on Beta 7 – Adding Technical Debt Reporting.
• June 3rd, 2013 – Released Beta 6 of the Database Health Reports.
• May 21st, 2013 – 600th download of the Database Health Reports. Going strong, thanks everyone.
• April 29th, 2013 – 500th download of Database Health Reports, lots of great feedback.
• March 27th, 2013 – The 400th download of the Database Health Reports.  Thanks everyone who is using the product.
• March 3rd, 2013 – Beta 5 Released with a new report for Big Clustered Indexes.
• February 17th, 2013 – The 300th download of the Database Health Reports.  Thanks everyone who is using the product.
• January 10th, 2013 – Beta 4 of the Database Health Reports released.
• November 18, 2012 – Release of the historic waits reporting, in Beta 3.
• November 1, 2012 – Cleanup on the historic waits reporting, preparing for Beta 3.
• October 29, 2012 – Refined the 5 dimensions of drilldown, making it work smoother.
• October 28, 2012 – Overall performance tuning on the database health application, getting cleaned up for Beta 3.
• October 27, 2012 – Added the 5 dimensions of drill down into the historic charting.
• October 24, 2012 – Spending some time fixing a few reports that crashed on SQL Server 2005.  I think we are good with SQL Server 2005 now.
• October 20, 2012 – Added wait time monitoring, focusing on the queries that have the most waits.
• October 14, 2012 – Finally have the preliminary historic reporting working.
• October 11, 2012 – Major re-design of the application to focus now on historic reporting, rather than just the real time snapshot.
• September 30, 2012 – Release of Beta 2.  First download 15 minutes after posting.
• September 23, 2012 – Additional feedback from beta testers.  More fixes and adding the Connections Advisor as part of Beta 2.
• September 4, 2012 – First round of feedback from the beta testers.  So far so good, doing what I can to fix everything and add new features.
• September 3, 2012 – Started working on the new features that will eventually be part of the Beta 2 release of the Database Health reports application.
• September 2, 2012 – First International download of the Beta 1 release of the Database Health reports application 20 minutes after release.  It was downloaded from France.
• September 1, 2012 – First download of the Beta 1 release of the Database Health reports application 20 minutes after release.
• September 1, 2012 – Beta 1 release of the Database Health reports application.
• August 2012 – Final testing on the Database Health reports application and final prep for the beta release.
• July 2012 – Started testing on the Database Health reports application internally and preparing for the beta release.
• April 2012 – Gave up on the SSRS version of the database health reports and began working on an the full Database Health application.
• March 18, 2012 – Added 2 new reports Top Cache Queries and Top CPU Queries.
• March 16, 2012 –  A little more clean up and final polishing for SQL Saturday Vancouver tomorrow.
• March 11, 2012 – Minor UI Fixup.  Added included columns into the Exact Duplicate Indexes report.  Overall cleanup preparing for the SQL Saturday presenation of the SQL Server Health Reports next weekend.
• March 03, 2012 – Major UI Fixup.  Standard header on all pages, linking from any report to any other, ability to change the database from within the report, Updated help links, added Top IO report, fixed several bugs.
• January 08, 2012 – Fixed some layout issues in the Index Fragmentation Report, and cleaned up some general layout issues in the rest of the reports.
• December 10, 2011 – Fixed a couple of bugs in the backup set report with the line sizes in the chart.  Added the new Statistics report.
• December 08, 2011 – Released the backup set report
• December 07, 2011 – Released the database size report
• December 03, 2011 – Added CPU Utilization Report
• November 27, 2011 – Added Duplicate Index Report and Exact Duplicate Index Report
• November 26, 2011 – Added Long Running Queries Report
• November 19, 2011 – Created Initial Version using SSRS reports
• February to October 2011 – Initial planning – determining what queries would be useful in the Database Health Reports.