SQL Server – sysmaintplan_logdetail
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… Read More »SQL Server – sysmaintplan_logdetail
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… Read More »SQL Server – sysmaintplan_logdetail
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… Read More »SQL Server – Cost Threshold For Parallelism
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… Read More »Database Health Monitor Quick Scan Report
The check for MAX DEGREE OF PARALLELISM has be added to the Database Health Monitor – Quick Scan Report. The max degree of parallelism setting… Read More »SQL Server MAX DEGREE OF PARALLELISM
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:
Released March 20th, 2016.
It has been about 3 months since the last release, and I have added several new features, and many bug fixes.
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… Read More »Database Health Version 2.2 Released Today
The Quick Scan report in Database Health Monitor detects when you are performing SQL Server backups without compression, when the compression option is available. This applies to Full backups, Transaction log backups and Differential backups.
Not using compressed backups? Why not?
There are a couple minor drawbacks, the compressed backups take more CPU, not much more, but a tiny bit more. Also the compressed backups don’t compress very much when your database is using Transparent Data Encryption (TDE).
As part of the Database Health Monitor version 2.1 release there were many new report includes, one of those was the backup status report. A… Read More »Featured Report: Backup Status Report
I have just released version 2.1 of Database Health Monitor, this release involved 2 months of development since version 2.0 was released in July. People… Read More »Database Health Monitor version 2.1 Just Released
In the next week or two, I will be releasing version 2.1 of the Database Health Monitor application. I am just going through the final testing process now to get it ready for general release. There are a number of new features that have been requested since the release of version 2.0 that will be coming out in version 2.1. The most request feature was the addition of support for the F5 key to refresh reports. There have been several new server or instance level reports added, along with a new section to link to the instance level reports.
Here is a list of the newly requested features that are complete, and will be available in version 2.1 of the Database Health Monitor.