Monitors the Cross-database Ownership Chaining Enabled setting for the database. Note that this monitor is disabled by default. Use overrides to enable it when necessary.
Knowledge Base article:
Summary
This monitor checks the DB Chaining database setting. Since this monitor is part of the overall standard requirements, an alert would be generated if the setting does not meet the specified standard.
Configuration
The DB Chaining setting controls whether the database can be accessed by external resources, such as objects from another database. When the DB Chaining setting is ON, a database can be the source or target of a cross-database ownership chain.
To minimize the security surface area and to prevent certain spoofing scenarios, DB_CHAINING should be OFF. You should only have it ON if you are sure that your application requires it.
DB_CHAINING {ON | OFF}
Causes
A warning alert will be raised if the option does not match the required setting. Out of the box, the monitor is configured to alert when this setting is set to “ON”.
Resolutions
This issue may be resolved by:
Changing the configuration setting for this database to match the expected value.
Overriding the expected value for this unit monitor for this specific database or all databases.
Alternatively, if this monitor is not of concern for this database:
Disabling the monitor using overrides for this specific database or all databases.
Disabling the top-level aggregate configuration monitor using overrides for this specific database or all databases.
Expected value of database configuration setting. To view the set of applicable values please refer to "Configuration" section of the knowledge base article of this monitor.
OFF
Generates Alerts
Defines whether the workflow generates an Alert.
Yes
Interval (seconds)
The recurring interval of time in seconds in which to run the workflow.
43200
Synchronization Time
The synchronization time specified by using a 24-hour format. May be omitted.
Timeout (seconds)
Specifies the time the workflow is allowed to run before being closed and marked as failed.
300
Timeout for query execution (seconds)
The workflow will fail and register an event, if the query execution takes longer than the specified period.
60
Timeout for database connection (seconds)
The workflow will fail and register an event, if it cannot access the database during the specified period.
The Cross-database Ownership Chaining Enabled setting for database "{2}" on SQL Server instance "{1}", computer "{0}" is not set according to the best practices.
Home
ENU