Select Page

Download

The October 28, 2017 download of Database Health Monitor now available. Download today.

Download Database Health Monitor

October 28, 2017- Version 2.6.1 (920):  DatabaseHealth_October_28_2017.zip  <<– Download Link

  • Download the zip file
  • Open the zip file, and run DatabaseHealthSetup.exe.

If you have been using a previous version of Database Health Monitor, just download and install this version over the previous one.

Thank you for using Database Health Monitor.  Give us your thoughts by filling out our User Survey.

What People Are Saying About Database Health Monitor

  • I would like to thank you for sharing this product with us free. I have installed and using health monitor on my production DB.  very very nice…. Thank you so very much. I hope you will keep adding more features in this product. Well done  (Rohit)
  • Outstanding app. Already referred it to several friends in the field. Well I do have to say the changes you have made (regarding version 2.5), seems to have made everything in the interface much snappier. Your work here is quite impressive. (Frank from Texas)
  • Outstanding! Besides enjoying the layout of your app, one thing I really like about the Quick Scan Report is each entry has a corresponding link that discusses the finding so I can go back and review recommendations, cautions, etc. (Michael)

Version 2.6.1 Release Notes

Version 2.6.1 is the October 28, 2017 release of Database Health Monitor.

Bug Fixes in 2.6.1

  • Bug fixed with the Disk Space Report not showing the disk free space in on SQL Server 2008R2.
  • Fixed a bug with the new inventory report where it was not showing information on SQL Server 2005 and 2008 instances. It has been fixed now for all SQL Server versions 2005 and newer.
  • Quickscan report was reporting extra errors in the error log for servers that have memory error recovery enabled. Eliminated this message from the Quickscan report.

 

Version 2.6 Release Notes

Version 2.6 is the October, 2017 release of Database Health Monitor

New Features in 2.6

  • Added a Job Schedule instance level report.
  • Added an option on the statistics report to show statistics for all databases, and to generate the script to rebuild statistics for all databases. (Customer request)
  • Added a Quick Scan Report check for logins that have a non-existent default database.
  • Added a Quick Scan Report for SQL Server Express Edition, and display a warning.
  • Modified the database mail check in the Quick Scan Report to display a different message when it detects that database mail is not enabled if the SQL Server is running express edition.
  • Modified the Blocked Queries report to better show the blocking query and to differentiate it from those being blocked.
  • Added a Quick Scan Report check for SQL Agent Jobs with no notification on failure.
  • Updated the link to the support site. It now goes to http://support.sqldatapartners.com which is vastly improved over the previous support site.
  • Added a Quick Scan Report check for power settings, recommending that a High Performance option be used.

Bug Fixes in 2.6

  • Fixed a bug when clicking on a database to drill down on the queries needing params report. Previously it was crashing, now it has been fixed.
  • Fixed a bug in the database overview incorrectly reporting unused indexes.
  • Fixed a bug in the server overview panel when displaying the machine or VM type where it was failing on SQL 2012.
  • Fixed a bug with the “Instance Reports” title overlapping the buttons to get to the instance reports on certain resolutions with larger fonts.
  • Fixed some timing related bugs on the Blocked Queries report. It was erroneously showing blocked queries without the query blocking them being shown.
  • Fixed various bugs around compatibility level 70 and 80 and crashing on some of the reports. Yes, people are still running databases at level 70 and 80.
  • Fixed a bug on the server overview page on very large databases, greater than 1TB causing the query to crash.

See the Release Notes page for details on updates in older versions.

Database Health Monitor

 

47 Comments

  1. Francis

    I was working on building my own application (for learning purposes and for practical use) using DMVs and came across your app. Very nice application! Nice Application!

    Reply
  2. Michael

    Love the new version.

    Reply
  3. Dinesh Modi

    Hello Steve, 8.1 has expired. Any plans for 8.2? I really rely on this tool for doing a lot of maintenance on my database and will appreciate a new version or for the expiry check to be removed from the existing version. Thanks in advance for your consideration.

    Reply
  4. Bojan

    Hi,
    Beta 8.1 expired, no new version, old one does not work.
    What to do?

    Best regards
    Bojan

    Reply
  5. deleor

    Now, I must tell you, this is one of the best tool I’ve used- Dele

    Reply
    • Steve Stedman

      Thanks for the feedback. I appreciate it.

      Reply
  6. SYed

    Its pretty cool and useful. i would like out to print out the report. is there any option ?

    Reply
    • Steve Stedman

      Printing is something that we have on the to do list. It is not yet available.

      Reply
  7. Daotman

    I get Beta expired and can’t open the app even after downloading the latest version

    Reply
  8. Eugene van den Bergh

    Thanks for the great product Steve, you make our lives so much easier, thanks for all the time and effort you put into making our lives easier. Just wanted to check with you if there was any probability of a version with web interface anywhere in the pipeline ?

    Reply
    • Steve Stedman

      I am not currently working on a version with a web interface, but it is a good idea. Thanks!

      Reply
  9. Rui Bastos

    It’s the first time I see so many useful DMVs packed together in a easy way! Funny thing: it “complains” about Holla Halagreen backup scripts because they’re too long 🙂

    Reply
    • Steve Stedman

      I know that the scripts from Ola Hallengren are awesome, and I recommend them all the time. Sometimes you just need to exclude some functions or stored procedures from the technical debt check.

      Reply
  10. Dennis Nielsen

    Which SQL versions are supported?

    Reply
    • Steve Stedman

      SQL Server 2005, SQL Server 2008, SQL Server 2008R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016 are all supported in Database Health Monitor.

      There are a few minor features that don’t show up with SQL Server 2005 as the functionality required was not available in SQL Server 2005.

      Reply
  11. dao

    Is there a way to disable automatic servers connections on start up?

    Reply
    • Steve Stedman

      Currently there is not, but that is a great idea. I have added this to my list of things to work on.
      Thanks for the suggestion.

      -Steve Stedamn

      Reply
  12. Andrey

    Hello!
    Thank you for the product Steve!
    Could you add support AlwaysON AG? Definition when you connect? Report, status, recommended, etc. May be Best Practice.

    Reply
    • Steve Stedman

      Andrey, your suggestion has been added to the product backlog or our To Do List. If you have an specific details on what you are looking for that would be helpful as we decide what to include in the next release.

      Thanks,
      Steve Stedman

      Reply
  13. Andrey

    Example: Connect to listner – In the main window is displayed in which the replica is connected (in the case of the FCI – which Noda). – When you go to an instance to display the number of nod/replicas and their statuses, as well as AG. To add a report on the database status information in AG. Could be something else. Same question for DB DBHealthHistory. As pravino to add it in AlwaysON? will work correctly if you create it on the primary replica, and then add to the availability group? The correct statistics will be in this database?

    Reply
    • Andrey

      T add database DBHealthHistory to AlwaysON AG. Push TestConnection.

      5. Testing monitoring process from sql-aotest-list local.
      ERROR: The OLE DB provider “SQLNCLI11” for linked server “sql-aotest-list” reported an error. Authentication failed.
      Cannot initialize the data source object of OLE DB provider “SQLNCLI11” for linked server “sql-aotest-list”.
      OLE DB provider “SQLNCLI11” for linked server “sql-aotest-list” returned message “Invalid authorization specification”.
      OLE DB provider “SQLNCLI11” for linked server “sql-aotest-list” returned message “Invalid authorization specification”.

      Reply
      • Steve Stedman

        For versions 2.1 to 2.4.1 there was a problem with the linked server being created from the monitoring instance. If you download version 2.4.2 (860) or newer, delete the linked server called sql-aotest-list and then restart the database health historic wait monitoring, that should fix the linked server issue.

        Reply
  14. dao

    I am on version to 2.4.2 , how do I enable the new features for SSRS ?

    Reply
    • Steve Stedman

      On version 2.4.2 (or newer) just navigate to the instance running the Report Server Database, and click on the ReportServer database in the heirarchy. The overview page for the report server database will show the new reporting for SSRS.

      -Steve Stedman

      Reply
      • dao

        That does not seem to work if the name of the reporting database is not the default name of ReportServer

        Reply
        • Steve Stedman

          Yes, I discovered the same thing. that will be fixed in the 2.4.3 release. Sorry about that.

          -Steve Stedman.

          Reply
          • Steve Stedman

            This has been fixed in the July 2016 release of Database Health Monitor version 2.4.3.

  15. Baine

    Awesome. Good stuff Steve! Yet again.

    Reply
  16. Ashok Mehan

    do you have a mac version?

    Reply
    • Steve Stedman

      No… Sorry, but no Mac version.

      -Steve Stedman

      Reply
  17. Ian

    I constantly get this error when trying to set up a central/historical monitor DB:

    Starting test…

    1. Testing HistoricDB connection (trl-apex-00\apex).
    HistoricDB connection is good.

    2. Testing configuration for (trl-apex-00\apex).
    ERROR: Incorrect syntax near ‘)’.

    I cannot figure out where the issue is, I have tried with and without the instance name, with and without the port, etc…

    Please help I love this tool

    Reply
    • Steve Stedman

      Does the server have parenthesis in the name? (servername\instance) ?

      As a test, can you try connecting by IP address?

      Reply
  18. Javeed Ahmed

    Dear Steve,
    Thank you for this wonderful tool.
    I have a question.
    When I run the Disk Space report it does not show data in Total Size and Percent Free columns.

    Thanks
    Javeed

    Reply
    • Steve Stedman

      What version of SQL Server are you using. That information wasn’t available prior to SQL Server 2008 R2. Let me know. If it is newer than 2008R2 it might be something that I need to look into.
      -Steve Stedman

      Reply
  19. Jason Oliver

    Is there a newer version that can run on Windows 10?

    Reply
    • Steve Stedman

      Database Health Monitor normally runs fine on Windows 10, and has since right after Windows 10 released. I run it on Windows 10 every day.

      If you are having a specific problem running it on Windows 10, please open a support ticket at http://support.sqldatapartners.com and I will be happy to help track down what is not working.

      -Steve Stedman

      Reply
  20. pasquale

    Hi Steve, ” SELECT * ” when used in EXISTS clause should not be considered as a Tech Debt, do you agree?
    Regards,

    Reply
    • Steve Stedman

      Yes, I would agree. I need to get back in and do some more work on the Tech Debt section. It has been a while since I have worked on that.

      Reply
  21. Oleg

    How to file a bug report?
    Some features not work for me, app just freezes and unresponsive.

    Reply

Trackbacks/Pingbacks

  1. » It is finally here. Beta 1 of the Database Health Reports for SQL Server. Steve Stedman - [...] Today (September 1, 2012) I have released the Beta 1 of the Database Health reports project. [...]
  2. » Working on Beta 2 of the Database Health Reports Steve Stedman - [...] has been a good acceptance of Beta 1 so far, and with feedback here are some of the things…
  3. » Finding tables that don’t have a clustered index. Steve Stedman - [...] Take a look give it a try.   This report will be in Beta 2, which will be available…
  4. » Finding the contents of the Plan Cache Steve Stedman - [...] do I find the contents of the SQL Server Plan Cache?”   My first response is just use the…
  5. » Database Health Beta 2. Stedman Solutions - [...] Today we released Beta 2 of the Database Health Project. [...]
  6. » Database Health Reports – Historic Waits Report Sneak Preview Steve Stedman - [...] now please download Beta 2 of the Database Health Reports or register on this site and you will be informed…
  7. » Reminder… Please Register for Beta 3 Steve Stedman - [...] Wait Monitoring.  Here is an example screen shot of the Historic Wait Monitoring.  Beta 3 of the Database Health Reports…
  8. » Unleashing Common Table Expressions in SQL Server – Slides and Sample Code Steve Stedman - [...] Here is a preview of the Query Waits Advisor, which will be available soon in Beta 3. [...]
  9. » Unleashing CTEs in SQL Server – Slides and Sample Code – Olympia SQL Saturday Steve Stedman - [...] Here is a preview of the Query Waits Advisor, which will be available soon in Beta 3. [...]
  10. » Beta 3 is Now Available. Steve Stedman - [...] 18, 2012 by SteveStedman Leave a Comment Download this page in PDF formatOne big new feature…
  11. » Beta 4 of the Database Health Reports Steve Stedman - [...] http://databasehealth.stevestedman.com/download/ [...]
  12. » Over 300 Dowloads of the Database Health Reports Steve Stedman - [...] If you haven’t tried out the Database Health Reports project you can get it from the FREE download page. [...]
  13. » Database Health Reports – Beta 5 Released Today. Steve Stedman - [...] The Database Health Reports application provided free of charge to the SQL Server community. Enjoy! [...]

Submit a Comment

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

To prove you are not a robot: * Time limit is exhausted. Please reload CAPTCHA.