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.

From the Blogs
business people around a table and laptop
Oct 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 10: Dynamic Detection Gotcha #3

You can interject a SQL Server Job Step into your Jobs and have this new/injected Job Step do some checking for you. Here's a look at everything that’s involved in such an approach....More
Man holding a piece of paper with the word GOTCHA
Oct 7, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 9: Dynamic Detection Gotcha #2 3

Given that a USE statement is parsed before code is actually run, there are a few options that could be used as a around when it comes to detecting whether or not code should be run....More
iceberg
Oct 2, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 8: Dynamic Detection Gotcha #1 1

Learn about why the option of dynamically detecting whether or not to run a SQL Server Job at execution time is quite a bit more problematic than you might think....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) ×