Welcome to Minion CheckDB
Our new DBCC CheckDB module for Minion is out, and it’s everything we wanted it to be! Download this free module, install on any number of servers, peruse the documentation, and fall in love with integrity checks all over again.
Minion CheckDB completes the MinionWare maintenance and backups suite in style. Each solution is plug-and-play for the busy DBA, and deeply configurable for those shops with in-depth needs.
Watch the Introduction to Minion CheckDB Webinar for highlights of the product’s features!
This new module is MinionWare’s most ambitious free release yet, featuring all of the rich scheduling and logging functionality in previous products, plus remote CheckDB, multithreading, custom snapshots, rotational scheduling, and more.
Minion CheckDB is a stand-alone database integrity check module. Once installed, Minion CheckDB automatically checks all online databases on the SQL Server instance, and will incorporate databases as they are added or removed.
Some of the very best features of Minion CheckDB are, in a nutshell:
- Dynamic Thresholds – Minion CheckDB allows you to automate whether databases get a DBCC CheckDB operation, or a DBCC CheckTable operation.
- Remote CheckDB – Automatically run DBCC CheckDB remotely for any database.
- Dynamic Remote CheckDB – Allows you to set a tuning threshold, so the CheckDB will run remotely only if it is above that threshold.
- Custom Snapshots – Choose to create a custom snapshot, for versions of SQL Server that support custom snapshots. This allow you to determine where your snapshot file(s) will be located.
- Custom Dynamic Snapshots – For CheckTable operations, you can configure “rotating” dynamic snapshots that drop and recreate every few minutes.
- Multithreaded database processing – Run multiple DBCC CheckDB operations in parallel.
- Multithreaded table processing – Run multiple DBCC CheckTable processes at the same time.
- Rotational scheduling – Minion CheckDB allows you to define a rotation scenario for your operations. For example, a nightly round of 10 databases would perform integrity checks on 10 databases the first night, another 10 databases the second night, and so on. 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.
- Operation ordering – Run DBCC CheckDB and CheckTable operations in exactly the order you need.
- Extensive, useful logging – Use the Minion CheckDB log for estimating the end of the current CheckDB run, troubleshooting, planning, and reporting. Errors are reported in the log table instead of text files.
- Run code before or after CheckDBs and CheckTables – This is an extraordinarily flexible feature that allows for nearly infinite configurability.
- Integrated help – Get help on any Minion CheckDB object without leaving Management Studio, with the Minion.HELP stored procedure.
- Clone Settings – Use the new CloneSettings procedure to generate template insert statements for any table, based on an example row in the table.
- Scenario testing — Test the settings to be used at any given time for any database.
- Automated installation – Run the Minion CheckDB installation scripts, and it just goes. You can even rollout to hundreds of servers almost as easily as you can to a single server.
- Granular configuration without extra jobs – Configure extensive settings at the default, database, and/or table levels with ease. Say good-bye to managing multiple jobs for specialized scenarios. Most of the time you’ll run MC with a single job.
- Live Insight – See what Minion CheckDB is doing every step of the way. You can even see the percent complete for each operation as it runs.
- Flexible include and exclude – Perform integrity checks on only what you need, using specific database names, LIKE expressions, and even regular expressions. Further restrict operations by including or excluding by schemas and/or tables.
- Inline Tokens – Inline Tokens allow you use defined patterns to create dynamic names. For example, MC comes with the predefined Inline Token “Server” and “DBName”.