Minion CheckDB provides remote integrity checks, where a database may be restored to another instance for DBCC CheckDB operations. This table allows you to define thresholds to prevent smaller databases from taking part in remote CheckDB operations.

Note: Remote operations only apply to DBCC CheckDB. MC does not support remote CheckTable.

Minion.CheckDBSettingsRemoteThresholds is very similar to Minion.CheckDBSettingsAutoThresholds, except that this table does not have a ThresholdMethod column; the method here will only ever be size.

To turn on this feature, Minion.CheckDBSettingsDB IsRemote must be set to 0. While this may seem counterintuitive, IsRemote = 1 turns on remote CheckDB for all databases (that the given row applies to). If you wish to handle remote operations dynamically, based on database size, set IsRemote = 0 – meaning, “I want operations to be local unless a database crosses the threshold”.

For full instructions on configuring remote CheckDB, see the remote thresholds section of “How to: Set up CheckDB on a Remote Server”. Also see “About: Remote CheckDB”.
Name Type Description
ID int

Primary key row identifier.
DBName varchar

Database name.
ThresholdType varchar

The threshold type, as it relates to ThresholdMethod.

 

NULL (this is the same as Data)

Data

DataAndIndex

File
ThresholdMeasure varchar

The measure for our threshold value.

 

Valid inputs:

GB
ThresholdValue int

The correlating value to ThresholdMeasure. If ThresholdMeasure is GB, then ThresholdValue is the value – the number of gigabytes.
IsActive bit

Whether the current row is valid (active), and should be used in the Minion CheckDB process.