Secrets to Fast Detection and Recovery from Database Corruptions
How can you tell whether your data is corrupt? If you have corruption, how do you work out what's wrong with the database? How do you ensure you have a valid backup? If you don't have a valid backup, how and what do you repair? If you do have a backup, how do you work out whether you should restore or repair? And at what granularity? How do you go about determining what went wrong in the first place? It's all about limiting downtime and data-loss when a corruption occurs—from knowing the tools, to understanding the choices, to planning a successful strategy. Some of the features discussed in this session are: torn-page detection and page checksums, IO read-retry, backup checksums, consistency checks (DBCC CHECKDB and related commands), and database repairs. Facing database corruption is almost inevitable in every DBAs career—make sure you're prepared when it happens to you.
Cristian Andrei Lefter, SQL Server MVP
MCT, MCSA, MCDBA, MCAD, MCSD .NET,
MCTS, MCITP - Database Administrator SQL Server 2005
http://sqlserver.ro