Jess Pomfret has an initial use case for dbachecks:
Each check has one unique tag which basically names the check and then a number of other tags that can also be used to call a collection of checks.
For this example we are going to use several checks to ensure that we meet the following requirements:
- Full backup once a week – using LastFullBackup
- Differential backup once a day – using LastDiffBackup
- Log backup every hour – using LastLogBackup
Since each of the three checks we want to run also have the LastBackup tag we can use that to call the collection of checks at once.
Jason Squires looks at this for enterprise reporting:
This module was developed and designed to ensure you can see if you have the best settings/configurations set up on your SQL systems using powershell. There are three pre-requisites that are required to load the module. Those are Pester 4.3.1, PS Framework 0.9.10.23, and currently as of this post dbatools 0.9.207. However, the team of dbachecks, kindly built in a notification for you if those modules and versions should those not be installed or would have a need to update.
What I really love about this module, is how you can utilize SQL CMS, and view the results at an enterprise reporting level.
Shane O’Neill has a bit more:
Straight away, dbachecks gives you the option to include or exclude checks that you feel aren’t for you. If you only want to run a subset of the checks, then you can specify that.
The real beauty that I think dbachecks provide is that you are getting a wealth of checks for things that you may never have thought of checking or known how to check while being able to add any personal tests as well.
Sounds like something for DBAs to check out.