Database corruption happens all the time, all over the world. Learn how to easily and automatically detect corruption, and then how to recover from corruption with the minimum of downtime and data loss using restore or repair, applicable to anyone who is responsible for SQL Server databases, from SQL Server 2005 onward
Database corruption happens all the time, all over the world. When it happens in your environment, do you know what to do? Will you realize you have corruption? Written and presented by the person who wrote SQL Server's consistency checking and repair tools, this course will show you what you need to know to detect and recover from most cases of database corruption. The course starts by explaining why timely corruption detection is so important, and then investigates the various causes of database corruption. You'll learn how to configure SQL Server to automatically detect when I/O errors occur, what consistency checks are, the DBCC commands to use to perform consistency checks, and how to configure SQL Server to perform consistency checks regularly. The course then moves on to interpreting the output from consistency checks so you'll know when you have corruption in your environment, plus whether and how the corruption limits your recovery options or not. Finally, the course ends with modules that describe and demonstrate how to recover from corruption using simple restore techniques and simple repair techniques. Packed with a wealth of information and practical, easy-to-follow demonstrations, this course will prepare you to detect and recover from database corruption when it happens to you. The course is applicable for all SQL Server versions from SQL Server 2005 onward, and for anyone responsible for SQL Server databases with any level of experience.
Paul is the CEO of SQLskills.com, a Microsoft Regional Director and a SQL Server MVP. He worked on the SQL Server Storage Engine team at Microsoft from 1999 to 2007. Among other things, he wrote DBCC CHECKDB/repair for SQL Server 2005 and was responsible for the Core Storage Engine during SQL Server 2008 development.