The dbcc checkstorage command:
Uses a named cache so that running it on the target database does not interfere with concurrent use of that database
Scales linearly with the aggregate I/O throughput
Does not lock tables or pages for extended periods, which allows dbcc checkstorage to locate errors while allowing concurrent update activity
Combines many of the checks provided by the other dbcc commands
Provides a detailed description of space usage in the target database
Separates the functions of checking and reporting, which allows custom evaluation and report generation
Records dbcc checkstorage activity and results in the dbccdb database, which allows trend analysis and a source of accurate diagnostic information for support
See Chapter 18, “Checking Database Consistency,” in the System Administration Guide for more information on dbcc.
