Session 3: Handling Corruption

RSS

Presented by: Robert Davis Running Time: 59 min Corruption can happen no matter how much care we take to prevent it. It’s inevitable, so the best course of action is to be ready for when it does happen. We will learn in the earlier sessions how to detect corruption, and now it’s time to learn what to do once you have identified it. We will explore the different types of corruption and the options for handling each type … without data loss.

Buy This On-Demand Training Now!

This video is part of the Data Integrity and Corruption: A Hard Road to Recovery On Demand training.

Data integrity and corruption can be a complex and scary topic. At some point in your career as a DBA, you will be faced with a potential data loss scenario due to deletion (accidental or not) or corruption. You can’t avoid it. You can only prepare for it and be ready to handle it when it occurs.

Already purchased this? to view your content.
Upcoming Conferences

Register now to get the best rate available!

From the Blogs
Save money red computer keyboard key
Jul 30, 2014
blog

When More Expensive Processors Actually Cost Less

Smart organizations are always looking for ways to cut costs when it comes to licensing SQL Server. Here are two ideas, or options, to save money....More
Health check note on computer keyboard
Jul 28, 2014
Sponsored

Grasp the Business Value of a Complete SQL Server Health Check

A comprehensive SQL Server health check will provide you with a better understanding of your complex database environment, and delivers answers you need....More
Baby duck swimming alone
Jul 15, 2014
blog

The Marginalization of SQL Server Standard Edition 5

Microsoft seems to be bent on marginalizing SQL Server Standard Edition—both in the sense of the artificial constraints placed upon how much memory it can use, and in terms of what seems to be a shift in focus on the role of Standard Edition from Microsoft....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×