IMPORTANT: Minion.CheckDBSettingsDB must have settings for CHECKTABLE operations defined. This table is used to define individual exceptions.
For more information on DBCC CheckTable options, see the DBCC CheckTable article on MSDN: https://msdn.microsoft.com/en-us/library/ms174338.aspx
Name | Type | Description |
---|---|---|
ID | int |
Primary key row identifier. |
DBName | varchar |
Database name. Required. |
SchemaName | varchar |
Schema name. Required. |
TableName | varchar |
Table name. Required. |
IndexName | varchar |
This field is not yet in use. |
Exclude | bit |
Exclude database (or, if specified, the specific table) from operations.
For more on this topic, see “How To: Exclude databases from operations” and “Include and Exclude Precedence”. |
GroupOrder | int |
The operation order within a group. Used solely for determining the order in which tables should be processed.
By default, all tables have a value of 0, which means they’ll be processed in the order they’re queried from sysobjects.
Higher numbers have a greater “weight” (they have a higher priority), and will be processed earlier than lower numbers. We recommend leaving some space between assigned order numbers (e.g., 10, 20, 30) so there is room to move or insert rows in the ordering.
For more information, see “How To: Process databases in a specific order”. |
GroupTableOrder | int |
Group to which this table belongs. Used solely for determining the order in which tables should be processed.
By default, all tables have a value of 0, which means they’ll be processed in the order they’re queried from sysobjects.
Higher numbers have a greater “weight” (they have a higher priority), and will be processed earlier than lower numbers. The range of GroupTableOrder weight numbers is 0-255.
For more information, see “How To: Process databases in a specific order”. |
DefaultTimeEstimateMins | int |
How long you estimate the operation will take, in minutes.
If you want to limit the operation based off of time (e.g., run for two hours), and the table has never been run before. So, the system has no way to know how long the operation will take. |
PreferredServer | varchar |
For remote CheckDB runs, the name of the remote server. |
TableOrderType | varchar |
Order the table using different metrics, such as size, usage, etc.
This field is not yet in use. |
NoIndex | bit |
DBCC CheckTable option NOINDEX. Specifies that intensive checks of nonclustered indexes for user tables should not be performed. |
RepairOption | varchar |
The repair option to use.
This field is not yet in use.
Future valid values may include: NULL NONE REPAIR_ALLOW_DATA_LOSS REPAIR_FAST REPAIR_REBUILD |
RepairOptionAgree | bit |
Signifies that you agree to the repair option specified in the RepairOption column. This is in place because some repair options (i.e., “REPAIR_ALLOW_DATA_LOSS”) can cause you to lose data.
This field is not yet in use. |
AllErrorMsgs | bit |
DBCC CheckTable option ALL_ERRORMSGS. |
ExtendedLogicalChecks | bit |
DBCC CheckTable option EXTENDED_LOGICAL_CHECKS. |
NoInfoMsgs | bit |
DBCC CheckTable option NO_INFOMSGS. Suppresses all informational messages. |
IsTabLock | bit |
DBCC CheckTable option -tablock. Causes DBCC CHECKTABLE to obtain a shared table lock instead of using an internal database snapshot.
IMPORTANT: We do not recommend using tablock on production systems! |
ResultMode | varchar |
This determines how much detail of the integrity check results to keep in the Minion.CheckDBCheckTableResult table.
NULL and SUMMARY will keep only the rows like ‘CHECKDB found%allocation errors and %consistency errors in database%’.
FULL will keep everything from a run.
NONE keeps nothing from a run.
Valid values: NULL (this is the same as SUMMARY) SUMMARY FULL NONE |
IntegrityCheckLevel | varchar |
DBCC CheckTable option. This controls whether or not you include physical only, data purity, or neither.
Valid values: NULL PHYSICAL_ONLY DATA_PURITY |
HistRetDays | int |
Number of days to retain a history of operations (in Minion CheckDB log tables).
Minion CheckDB does not modify or delete information in system tables.
Note: This setting is also optionally configurable at multiple levels. So, you can keep log history for different amounts of time for one database vs another. |
TablePreCode | varchar |
Code to run for a table, before the operation begins for that table.
For more on this topic, see “How To: Run code before or after integrity checks”. |
TablePostCode | varchar |
Code to run for a table, after the operation begins for that table.
For more on this topic, see “How To: Run code before or after integrity checks”. |
StmtPrefix | nvarchar |
This column allows you to prefix every integrity check statement with a statement of your own. This is different from the precode and postcode, because it is run in the same batch. Whereas, precode and postcode are run as completely separate statements, in different contexts.
Code entered in this column MUST end in a semicolon.
For more on this topic, see “How To: Run code before or after integrity checks”. |
StmtSuffix | nvarchar |
This column allows you to suffix every integrity check statement with a statement of your own. This is different from the precode and postcode, because it is run in the same batch. Whereas, precode and postcode are run as completely separate statements, in different contexts.
Code entered in this column MUST end in a semicolon.
For more on this topic, see “How To: Run code before or after integrity checks”. |
BeginTime | varchar |
The start time at which this configuration applies.
IMPORTANT: Must be in the format hh:mm:ss, or hh:mm:ss:mmm (where mmm is milliseconds), on a 24 hour clock. This means that both ’00:00:00’ and ’08:15:00:000’ are valid times, but ‘8:15:00:000’ is not (because single digit hours must have a leading 0). |
EndTime | varchar |
The end time at which this configuration applies.
IMPORTANT: Must be in the format hh:mm:ss, or hh:mm:ss:mmm (where mmm is milliseconds), on a 24 hour clock. This means that both ’00:00:00’ and ’08:15:00:000’ are valid times, but ‘8:15:00:000’ is not (because single digit hours must have a leading 0). |
DayOfWeek | varchar |
The day or days to which the settings apply.
Valid inputs: Daily Weekday Weekend [an individual day, e.g., Sunday] |
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. |