Download

The latest release of Database Health Monitor now available. Download today.

  • 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.


What People Are Saying About Database Health Monitor

  • “I installed Database Health Monitor on many of my client’s SQL servers and believe it’s the best tool out there for SQL monitoring.” – Charles Ray – March 2022
  • This is a great application for SQL Server DBAing. We have a web based product but this one is so comprehensive, both high level and detailed. So much is available right at the click of a button, it is amazing! I am so grateful for the application, for the effort to build it, and the decision to share it. I know it has made me a better DBA, my organization has benefited from it, and I deeply appreciate all of that! Thank you! – Jesse – October 2021
  • Thank you a lot for this excellent application. I loved the “missing indexes” and “Statistics” section, it helps me to save time and effort for the weekly maintenance.
    Best Regards  November 2019
  • Database Health is the first tool that I pull up when someone calls and complains about slow performance in their applications, that be Dynamics NAV, Dynamics AX or even the webpages running slow. It saves me a lot of time finding the queries, missing indexes or what be it, causing the problem. This is by far the easiest and most effective tool to use, when searching for problems that need instant resolution. Thanx a million for your contribution to the SQL world.  September 2019.
  • This is an awesome tool to find issues and fix them or improve performance in areas that I didn’t even know we can.
  • 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)

Mid February 2024 – Version 1055 Release Notes

New Features

  • Added Upgrade Recommendations instance report.
  • Added double click event on the TempDB High Usage Usage report to show the full query.
  • Added double click event on the What is Active report to show the full query.

General Maintenance

  • Adjusted the heat map colors for the tempdb usage report to have to be above 2gb before showing red. Thus making low usage tempdb never show red.

Performance Improvements

  • Reduced the startup time by more than 90% when starting Database Health Montior with many SQL Servers connected. Even more so when your SQL Servers have many databases. The first time you click on a database is may take a moment longer, but the startup time is dramatically reduced. If you are using just 3 or 4 SQL Servers you may not notice the difference, but anyone connecting to more than 10 SQL Servers, or to SQL Servers with dozens or hundreds of database should see a significant improvement. For instance on a production system connected to 34 sql servers at varying locations the startup time was about 1 minute and 15 seconds. Now it is about 4 seconds.

February 2024 – Version 1052 Release Notes

New Features

  • Added columns to the IO by drive report to include average latency details. (Customer Requested)
  • Added check #212 into the QuickScan report. This report when SQL Server is not using all of the cores assigned to the system.
  • Added 5 more checks into the QuickScan report around default settings, and more on the number of cores the server is using.
  • Add 2 more checks into the QuickScan report specifically around the size of the DBHealthHistory database log file to prevent excessive growth.
  • New dynamic resizing on the gray buttons for the instance reports on the main instance page so that they fit better on narrow screens.
  • New TempDB High Use Report that can be accessed by the historic tree menu under TempDB or from a hot spot in the TempDB Heat map.

General Maintenance

  • Updated QuickScan check #28 for full recovery model databases with no log backup to exclude databases that are offline.
  • Updated some of the historic monitoring to purge older data more efficiently, allowing for longer term retention and a smaller DBHealthHistory database data and log file.
  • Updated check #18 on the QuickScan report for no recent backups to exclude databases that are offline.
  • On the blocking query email, each block was being shown multiple times in the history. Now just distinct blocks are being shown.
  • Set the maximum size on the DBHealthHistory to be 2gb rather than the default which is much larger. 2gb is probably overkill, but at least it has a limit to prevent it from getting too big if backups are not run and the database is in full recovery model.

January 2024 – Version 1039 Release Notes

New Features

  • Added a new TempDB Historic report. Shows the historic TempDB use by hour.

General Maintenance

  • On the Quick Scan, Deep Scan report, limiting the number of outdated statistics to 100, to limit the report when there are thousands of outdated statistics. After 100, it just says and XXX more outdated statistics.
  • Added Security report in the left/right navigation of instance reports.
  • Add info on how to see the labels and Navigation notes to Large Tables Report.
  • Improved formatting on the Enterprise Index Report. Fixing issues with the formatting with really long index names.
  • Updating a number of links to DatabaseHealth.com to use https:// instead of http://.
  • Update copyright to extend to 2024.

December 2023 – Version 1034 Release Notes

New Features

  • Added new agent job, tables and procedures in the historic monitoring to track index usage over time. The purpose for this is to be able to determine what indexes are not being used and to determine if over time they are safe to delete. The concept of worthless indexes come from this, meaning indexes that have lots of update and no seeks, scans or lookups. The flip side of that is we can use this data to analyze what are the most valuable indexes on the system. Meaning those that are providing the most seeks, scans and updates. The current version just has tracking, in the next update we will include new index reports to report on this data.
  • Rearranged all the indexing reports into a group called indexing.
  • Added new reporting for Worthless indexes, which if your historic monitoring is enable you will be able to see over time what are the indexes that are never being used.


General Maintenance

  • Add more description to the RESOURCE_SEMAPHORE description on the Waits Advisor page.
  • In Long running queries report, add help to show ms for Total Run Time, Longest Run, and Average Run.
  • Added text in performance viewer information boxes.
  • Speed improvements on the historic version upgrader. This is the component that keeps the DBHealthHistory database up to date with the latest version of the code.
  • Updated dark mode scheme for heat map reports.
  • Add more description to the RESOURCE_SEMAPHORE Waits Advisor page.

November 2023 – Version 1028 Release Notes

New Features

  • Added Resource and Resource Info to the What is Active report to help show more details on what is causing the wait.
  • Added check #211 into the Quickscan report. Checking for backups going to new locations.
  • Add more reports into the dark color mode, improving the overall look of the program in dark mode.

General Maintenance

  • Improved error handling on background threads. If a server connection is lost it attempts to reconnect rather than submitting a crash report.

Bug Fixes

  • Fixing bug #938 – issues with date spin issue on the history job. Job is now created with a more modern date, rather than 2012 as the start date.
  • Fixed bug with a vertical bar | in passwords causing server login to fail.

October 18, 2023 – Version 1026 Release Notes

General Maintenance

  • 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.

Bug Fixes

• Fixed a bug with a lost SQL Server connection not setting the reconnect option.

October 2023 – Version 1024 Release Notes

New Features

• Added QuickScan check #209 for slow error log access.
• Added QuickScan check #210 for full and differential backup files missing from backed up location.

Bug Fixes

• Fixed a bug in connect strings with a single quote in the password. These were causing connections to fail and have now been corrected.
• Change message color from black to red when there are No Results Found in a report. To be readable in normal and dark mode.
• Adjustment of Quickscan item #41 threshold to be 10,000 backup messages per database for a more reasonable notification point.
• Fixed a bug with the server overview / database by sizes report where it was throwing a crash report of the database was offline.
• Fixed a bug in the online error reporting to not send reports on connection timeouts caused by a slow SQL Server. This helps reduce the noise in our error reports and allows the team to focus on the right issues.

August 2023 – Version 1022 Release Notes

New Features

• Added QuickScan check #207 for too small of a SQL Server error log rollover size.
• Added ability to delete orphaned users from the orphaned users report if they are not mapped to any objects.

Bug Fixes

• Fixed a bug in the charts with integer size overflow on a couple of the reports, including the missing indexes report.
• Fixed a bug in many of the real time reports for specific databases where the report would crash when a user with insufficient permissions tried to access the report. Now instead details on the missing permissions are displayed.
• Fixed a bug in connect strings with a semicolon in the password. These were causing connections to fail, and have now been corrected.

June 2023 – Version 1018 Release Notes

New Features

  • Updated the licensing page to make it look less like an html 1.0 web page. Added updated links to purchase the product, and informative details.
  • Sped up the reconnect process. Previously if the application sat for more than 24 hours, the first click would cause all the database connections to refresh. That has been updated to happen during off hours, and when you click on the program for the first time after sitting for 24 hours it should be active immediately rather than waiting for SQL Server to reconnect. Massive speed improvement.
  • For databases that show up in the tree view as “disconnected”, when you click on one of those it attempts to reconnect. This is handy as the only way to that before was to refresh the entire tree view which would reconnect all databases.

Other Items

  • Updates to the licensing, and additional options for points.

May 2023 – Version 1015 Release Notes

New Features

  • QuickScan report, added an option to assign a Scan item to a user. If you assign item 52 to a user, then all item #52 on that instance get assigned to that user.
  • Additional features for our Daily Checkup Customers being able to snooze items on the Daily Checkup Report from the Quickscan right click menu.
  • Performance Monitor now starts tracking automatically when you open the application without needing to hit the start button.

Bug Fixes

  • Fixed a case sensitive query issue on QuickScan check #206 the check for SQL Server Express data files approaching their size limit.

April 2023 – Version 1009 Release Notes

Bug Fixes

A quick update after last weeks release with just one bug fix included. For those with paid licensing there was a bug that when an updated version is available that the licensing check fails, and shows that you only have one license. This has been fixed in version 1009.


• Fixed a problem with licensing, when a new update was detected, the licensing check did not succeed. Meaning that the licensing would not show the correct number of connections when there is an update available. This has been fixed going forward.

April 2023 – Version 1008 Release Notes

Updates

  • Updating version numbers for the latest version of SQL Server in the Quickscan report and other areas that check for updates being available.
  • Renamed the “Alas Database” popup menu to “Alias Server”, it was more accurate of a description.

Bug Fixes

• Quickscan Report: fixing case sensitive column name issue in the Quickscan report with case sensitive databases.
New Features

• Added a refresh button in the treeview on the database right click menu.
• Added check #206 to the Quickscan report. Looking for SQL Server express servers with file sizes approaching 10gb.
• Added 2 indexes to improve performance on the historic waits monitoring.

January 2023 – Version 1007 Release Notes

The January 2023 release of Database Health Monitor includes bug fixes and feature enhancements.

New Features

• Indexes added on the DBHealthHistory monitoring database for improved performance.

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


Enroll Today!
SteveStedman5
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!

66 Comments on “Download

  1. 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!

  2. 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.

  3. 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 ?

  4. 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 🙂

    • 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.

    • 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.

  5. 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.

    • 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

  6. 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?

    • 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”.

      • 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.

  7. 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

  8. 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

    • 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

    • 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

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

  10. After installing your application again it no longer does anything. The window pops up with the license agreement and I click I accept and then OK but then nothing happens and I see nothing running on my computer. Has anyone else experienced this?

    • Fred, I haven’t seen that issue. Perhaps there is something being blocked when it is trying to get the latest update. Have you confirmed that you are running on the latest version of Database Health Monitor.

      Send me an email with additional details, and I can help sort this out.

      -Steve

  11. Have you had issues where the license agreement comes up but after accepting the agreement, absolutely nothing happens. It just does not run.

    • Fred, I haven’t seen that issue. Perhaps there is something being blocked when it is trying to get the latest update. Have you confirmed that you are running on the latest version of Database Health Monitor.

      Send me an email with additional details, and I can help sort this out.

      -Steve

  12. Backup Status – > “No recent Full backup”. Can you add a column to show if this this a primary or secondary server in the AOAG?

  13. I tried to install version DatabaseHealth969 but it doesn’t even start to do anything, I tried to download again with the same behavior.

    I have windows 2016 server and SQL server Enterprise 2016 SP2 CU11.
    I also have Hebrew as another language in my keyboards.

  14. Hi Steve
    . great work Steve.
    It’s very helpful to me .
    But I have a problem with isolated and no internet domain :(/.
    all the times Ask License windows.
    Thanks,
    Leon

  15. Hi Steve, i can’t use the software because it ask me for code license, when i fill data for request code license nothing it happens and the form never close, even touching the button “Request Updated License code”, and although I touch the button “Done” the box reappears …..
    Please, do you help me?

  16. I was using the tool for a while but the collectors generated blockages with other tasks so I had to uninstall it from the whole environment. With the continuous update I hope that this problem is solved.
    I used it for about 4 months and honestly it is an excellent tool, I found it very useful, it is a great help to monitor all SQL instances in a centralized way and the information it provides is very helpful.
    I hope to have even better results this time.
    Thank you very much for contributing your knowledge for the general benefit, it is a great job, my respects.

    • Thanks for your comments Jose. Ove the last 10 years that I have been working on Database Health monitor we have certainly had some bugs along the way. Any of those older issues that were causing problems have been resolved.

      Have a great day!

      -Steve Stedman

Leave a Reply to Steve Stedman Cancel reply

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

*

To prove you are not a robot: *