You can also use the rotational scheduling to limit operations by time; for example, you could configure MC to cycle through DBCC CheckDB operations for 90 minutes each night.
This table holds the rotation scenario for your operations (e.g., “run CheckDB on 10 databases every night; the next night, process the next 10; and so on”). This table applies to both CheckDB and CheckTable operations.
For more information, see “About: Rotational Scheduling” and “How to: Configure Rotational Scheduling”.
| Name | Type | Description |
|---|---|---|
| ID | bigint |
Primary key row identifier. |
| DBName | varchar |
Database name.
Note that this field only applies to rows with OpName = ‘CHECKTABLE’. For CHECKDB rows, feel free to use ‘MinionDefault’ or leave it NULL. |
| OpName | varchar |
The name of the operation to be performed.
Valid values: CHECKTABLE CHECKDB |
| RotationLimiter | varchar |
The method by which to limit the rotation.
DBCount limits the number of databases processed in a single operation; this only applies to CHECKDB operations.
TableCount limits the number of tables processed in a single operation; this only applies to CHECKTABLE operations.
Time limits the operation by a number of minutes.
Valid values: DBCount TableCount Time |
| RotationLimiterMetric | varchar |
The metric by which the RotationLimiter is defined.
Each RotationLimiter has only one possible metric: DBCount and count, TableCount and count, Time and Mins (minutes).
Valid values: Count Mins |
| RotationMetricValue | int |
The number associated with the RotationLimiter, e.g., 10 for 10 databases, or 120 for 120 Mins. |
| RotationPeriodInDays | int |
This field is not yet in use. |
| IsActive | bit |
Whether the current row is valid (active), and should be used in the Minion CheckDB process. |
| Comment | varchar |
For your reference only. You can label each row with a short description and/or purpose. |