SQL Server optimizations for DBCC CHECKDB

Method 1,

A snapshot of the database before the DBCC CHECKDB is run (the transaction is consistent), the DBCC detects the snapshot, and the DBCC finishes deleting the snapshot.

The purpose of the snapshot is to not allow DBCC to request too many locks, from which you can see that DBCC can go in multiuser mode.

Method 2,

DBCC can also notify multithreading techniques to run faster. The side effect of this is that the normal connection may not be able to get enough resources during this time period.

Method 3,

You can use the PHYSICAL_ONLY option, which can check the physical consistency of the database with a small overhead. And check out the broken page that endangers the data security, hardware failure.

SQL Server optimizations for DBCC CHECKDB