Database Health Monitor – July 2016 Release

Download PDF

I have just released version 2.4.3 the July 2016 version of Database Health Monitor. You can download it now at the Database Health Monitor website. http://DatabaseHealth.com/download

Since the releases have been coming about monthly lately, I have decided to add the month and year to each release so that it has a bit more meaning. The next update should be sometime in August.

This update was about a month in the making, a few new features, a few bug fixes, and overall improvements.

My favorite new feature in this release is the addition of a “Go Back” feature when viewing reports. When you click from one report to another, and then another, and you realize that you want to jump back to that previous report… well you can now, just use the Backspace key on your keyboard from anywhere in database health monitor. Hit it multiple times to jump back further in your history of reports.

New Features in 2.4.3

  • Backspace button to go to the previous report viewed.
  • A new report for SSRS report servers that shows the speeds of the SSRS reports being run. You can find your slow SSRS reports with this.

Fixes in 2.4.3

  • With multiple historic monitoring instances, the CPU load by hour report was only showing the CPU load for the server doing the monitoring, not for the server being monitored.
  • Fixed a bug causing the database overview panel to crash for database instances that with a name that started with a space, or ended with a space. Example: [ DatabaseName ]  Note the spaces inside of the brackets.  It works now.

Download now at http://DatabaseHealth.com/download

Star_of_life

 

More from Stedman Solutions:

SteveStedman5
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!

2 Comments on “Database Health Monitor – July 2016 Release

  1. With multiple historic monitoring instances, the CPU load by hour report was only showing the CPU load for the server doing the monitoring, not for the server being monitored.

Leave a Reply

Your email address will not be published. Required fields are marked *

*