• Paul Randal (8/22/2011)


    Nice - but really only the equivalent of BACKUP DATABASE ... WITH CHECKSUM.

    I would strongly advise not using this for the same reasons I strongly advise not using BACKUP DATABASE ... WITH CHECKSUM as an alternative to DBCC CHECKDB - it will not detect errors introduced by memory problems, SQL Server bugs, or IO subsystem corruptions of pages using torn-page detection.

    Bottom line - you can't avoid running DBCC CHECKDB - don't fall into the trap of running something faster. Offload your checks to a non-production server but continue running DBCC CHECKDB - it's the only thing that will find all corruptions.

    Thanks

    I know this is really old post, would it be help if i run DBCC CHeckdb on a different server where databases are SAN replicated from the production? Would it find all the errors like as if i ran on prod db?