dbcc checkstorage runs checks against the database on disk.
Allocation of text valued columns
Page allocation and consistency
OAM page entries
An OAM page for each partition exists
Pointer consistency
Text-valued columns and text-column chains
If a corruption is only in memory, dbcc checkstorage may not detect the corruption. To ensure consistency between two dbcc checkstorage runs, execute checkpoint before running dbcc checkstorage. However, doing this may turn a transient memory corruption into a disk corruption.
Combines many of the checks provided by the other dbcc commands
Does not lock tables or pages for extended periods, which allows dbcc to locate errors accurately while allowing concurrent update activity
Scales linearly with the aggregate I/O throughput
Separates the functions of checking and reporting, which allows custom evaluation and report generation
Provides a detailed description of space usage in the target database
Records dbcc checkstorage activity and results in the dbccdb database, which allows trend analysis and provides a source of accurate diagnostic information
The dbccdb database to store configuration information and the results of checks made on the target database. However, you can run dbcc checkstorage from any database.
At least two workspaces to use during the check operation. See “dbccdb Tables” in the Reference Manual: Tables.
System and stored procedures to help you prepare your system to use dbcc checkstorage and to generate reports on the data stored in dbccdb.
dbcc checkstorage does not repair any faults. After you run dbcc checkstorage and generate a report to see the faults, you can run the appropriate dbcc command to repair the faults.