The tables in Minion CheckDB fall into four categories: those that store configured settings, those that log operational information, debug tables, and work tables.
The settings tables are:
- Minion.CheckDBSettingsAutoThresholds – This table allows you to set thresholds to automate whether databases get a CheckDB operation, or a CheckTable operation.
- Minion.CheckDBSettingsDB – This table contains the essential CheckDB and CheckTable settings for databases, including processing order, history retention, database pre-and postcode, native settings, and more. It holds settings at the default level, database level, and operation level. You may insert rows to define CheckDB/CheckTable settings per database (etc); or, you can rely on the system-wide default settings (defined in the “MinionDefault” rows); or a combination of these.
- Minion.CheckDBSettingsRemoteThresholds – This table allows you to define thresholds to prevent smaller databases from taking part in remote DBCC CheckDB operations.
- Minion.CheckDBSettingsRotation – 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”).
- Minion.CheckDBSettingsServer – This table contains server-level CheckDB settings, including schedule information. The primary Minion CheckDB job “MinionCheckDB-AUTO” runs regularly in conjunction with this table to provide a wide range of CheckDB options, all without introducing additional SQL Agent jobs.
- Minion.CheckDBSettingsSnapshot – This table holds the settings for database snapshots.
- Minion.CheckDBSettingsTable – Minion.CheckDBSettingsTable allows you to configure table-level exceptions to the CHECKTABLE settings defined in Minion.CheckDBSettingsDB.
- Minion.CheckDBSnapshotPath – This table allows you to configure snapshot file path settings for local custom snapshots. You can specify one row per snapshot file.
The log tables are:
- Minion.CheckDBLog – Holds an operation-level summary of integrity check operations. It contains one time-stamped row for each execution of Minion.CheckDBMaster, which may encompass several database level integrity check operations. This is updated as each CheckDB occurs, so that you have Live Insight into active operations.
- Minion.CheckDBLogDetails – Holds a log of CheckDB activity at the database level. This table is updated as each operation occurs, so that you have Live Insight into active operations.
- Minion.CheckDBResult – Keeps the results from DBCC CheckDB operations (as opposed to outcome and associated operational data in the “Log” tables).
- Minion.CheckDBSnapshotLog – This table keeps a record of snapshot files (one row per file). This includes files created as part of local custom snapshots, and as part of snapshot files created locally from a remote server’s “remote CheckDB” process.
- Minion.CheckDBCheckTableResult – This keeps the results from DBCC CheckTable operations (as opposed to outcome and associated operational data in the “Log” tables).
The debug tables are:
- Minion.CheckDBDebug – This table holds high level debugging data from Minion CheckDB runs where debugging was enabled.
- Minion.CheckDBDebugLogDetails – This table holds detailed debugging data from Minion CheckDB runs where debugging was enabled.
- Minion.CheckDBDebugSnapshotCreate – This table holds custom snapshot-related debugging data from Minion CheckDB runs where debugging was enabled.
- Minion.CheckDBDebugSnapshotThreads – This table holds thread-related debugging data from Minion CheckDB runs where debugging was enabled.
The work tables – which are for internal use, and so are not fully documented – are:
- Minion.CheckDBCheckTableThreadQueue – Information gathered in preparation for a CheckTable run is stored here.
- Minion.CheckDBRotationDBs – Internal use only.
- Minion.CheckDBRotationDBsReload – Internal use only.
- Minion.CheckDBRotationTables – Internal use only.
- Minion.CheckDBRotationTablesReload – Internal use only.
- Minion.CheckDBTableSnapshotQueue – Internal use only.
- Minion.CheckDBThreadQueue – Internal use only.