In order to break down database maintenance RockSolid will not by default issue a DBCC CHECKDB command, but will instead break database consistency checks down into their individual components, being a validation of the consistency of the catalog follow by a series of individual DBCC CheckTable commands. This approach allows RockSolid to more closely control the run-time flow of the deployed job, helping to ensure maintenance won't exceed allocated windows and also ensuring maintenance can stop and continue during the next maintenance window if the allocated time isn't sufficient to complete a full database check in one iteration.
While this approach allows greater control, by default SQL Server will take a database snapshot for each execution of the DBCC CheckTable command which can significantly extend the DBCC execution time frame. As an alternate approach, you can change the DBCC mode to "offline". This will instruct RockSolid to use the TABLOCK option with the DBCC CheckTable command. This prevents SQL Server from creating a database snapshot for each execution, however for the duration of each execution of DBCC CheckTable the relevant table will be locked under a shared lock which will block update activity.
If the database consistency checks are scheduled to occur during true maintenance window periods where users are not expected to be undertaking action on the database then offline DBCC's should be considered due to their improved execution time.