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 …
Today I released the latest update to Database Health Monitor. Version 2.4.2. It has been about a two weeks since version 2.4.1 release and version 2.4.2 has a few new features, and a couple bug fixes. Here is a preview of the new logins report. First the logins panel on the Server overview report. When you click the overview panel, you …
Database Health Monitor Version 2.4.2 Released Today Read more »
Just one day after releasing Database Health Monitor version 2.4, today I released version 2.4.1. Version 2.4.1 includes a bug fix and 2 new feature that were added after the release of version 2.4. Feature: Support for SQL Server 2016. Since SQL Server 2016 officially released yesterday, Database Health Monitor now supports SQL Server 2016. Bug: The check for the latest …
If you haven’t tried Database Health Monitor Version 2.4 might be a good time to try it out. Five and a half years of my development time has gone into Database Health monitor, and hopefully the features will show it. Here is what people have to say about Database Health Monitor. Excellent – It’s the first tool I open every morning …
The check for excessive sysmaintplan_logdetail has be added to the Database Health Monitor – Quick Scan Report. If you haven’t had a maintenance plan to clean up maintenance plan history, it can grow excessively over time. I recently worked on a SQL Server that had 6 years worth of maintenance plan history, and the msdb.dbo.sysmaintplan_logdetail table was approaching nearly 1gb in …
The check for Cost Threshold for Parallelism check has be added to the Database Health Monitor – Quick Scan Report. The Cost Threshold For Parallelism setting in SQL Server controls the level at which the query optimizer decides to have a query be processed using parallelism, or multiple threads. The default setting is 5 which may have made sense 15 years ago in …
With the updated release of Database Health Monitor yesterday, here is the updated list of documentation on the Quick Scan Report. All of the following (plus a few more) are checked from the Database Health Monitor Quick Scan report. The Quick Scan report checks some common problems that can cause grief on your SQL Server database, and reports on those, …
The check for MAX DEGREE OF PARALLELISM has be added to the Database Health Monitor – Quick Scan Report. The max degree of parallelism setting in SQL Server is used to control the maximum number parallel threads available to process your query. The default setting of 0 means use as many as possible. The problem with this default is that you …
With over 7500 downloads worldwide to date, I have just released the next installment of the FREE Database Health Monitor application. Here what one person had to say about it “Excellent – It’s the first tool I open every morning to see what is going on in my production environment! Thanks for the great work!” Download today: Database Health Monitor …
Today I have the pleasure of releasing the next version of the Database Health Monitor application. Currently at version 2.2, I have been working on this since 2011, and I have introduced some new features in the latest version. Visit the Database Health Monitor Download Page to get it for free today. The main page has been updated, with a …