Session 2: Recovering Lost Data

RSS

Presented by: Robert Davis Running Time: 51 min What do you do when someone forgets the WHERE clause on a delete statement or if a table gets accidentally dropped? We will look at ways to proactively prepare for the recovery of lost data and techniques for recovering the data after it has been lost, including techniques for mining the transaction log for the offending transactions.

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
Two women looking a man's computer monitor
Sep 17, 2014
Article

AlwaysOn Availability Groups and SQL Server Jobs, Part 6: High-Level Options and Rationale for Handling Batch Jobs

There are a couple of options for how we could handle batch jobs when Availability Groups are thrown into the mix....More
Sep 12, 2014
Sponsored

Managing a Healthy SQL Server Database: Three Principles We Overlook

In managing a database or sometimes numerous databases, we often get caught up in the day-to-day maintenance and lose sight of the other principles we know are critical to ensuring optimal performance. Here’s a quick refresher....More
Exclamation marke on yellow road sign
Sep 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 5: Setting Up Failover Alerts

Alerts represent a great way to take a proactive stance on being notified or alerted when something ugly, potentially ugly, or important happens on a SQL Server. On most servers that I manage, I typically deploy a whole bevy of different alerts....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) ×