Scoping the DBSS - Unavailable rule to exclude databases (4295742)

How can a rule be scoped so that it does not trigger for databases that are intended to be offline on a monitored instance.

For example to not be notified if "testDB2" is OFFLINE.

RESOLUTION 1 (for all OFFLINE databases)

WORKAROUND

The "DBSS - Unavailable" rule is scoped to the DBSS_Databases topology which does not include the specific details on the status of a SQL Server database. Values defined by the db_status property are either Available or Unavailable.

A custom rule could be created to use the DBSS_Database_Properties topology and the db_status string property. The statuses would either be OFFLINE or ONLINE for this property.

Please consult your Sales Representative or Quest Professional Services for details for specific assistance on a custom rule such as this.

STATUS

An Enhancement Request FGSS-I-43 has been logged with Quest Development to be considered for a future release in the SQL Server cartridge.

RESOLUTION 2 (for specific database names)

1. Navigate to the Database Dashboard.
2. Check the MSSQL instance then click "Administer Agents".
3. Click Databases Exclusion, then click the "Exclude Databases" button.
4. Use the dialog to add manually a MSSQL database, or select from the list of available, and move to the Excluded column.
5. Click the "OK" button.
6. Click the "Save changes" button, Agent properties are updated automatically.