No environment is exactly the same as any other environment, and thus one glove cannot fit all. For this, there is the configuration system, which allows the user to change any setting as desired:

Get-DbcConfig

For example, there is the popular dba procedure called WhoIsActive. Per default, dbachecks will test in relevant checks whether this procedure was installed on the master database. This is often the case, and thus, the baseline.

If, however, your organization prefers storing administrative procedures in a dedicated dba database, you will want to update this setting accordingly:

Set-DbcConfig -Name policy.whoisactive.database -Value dba

This setting will not only be immediately applied, the local computer will remember it for future sessions.

The configuration system comes with two extra commands that make all the difference where applied health tests are concerned: Export-DbcConfig and Import-DbcConfig. The former allows you to store the current configuration state in a JSON file, the latter allows you to import it again into a session.

Using configuration files, you can easily store and split up different sets of settings for different sets of tests:

# Export current settings
Export-DbcConfig -Path C:dbachecks_configproduction_config.json

# Import settings from file
Import-DbcConfig -Path C:dbachecks_configproduction_config.json -Temporary