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
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
Jul 8, 2014
blog

Replication: Sometimes More is Less

The unconventionality of having two publications for complex, unruly databases typically ends up saving huge amounts of time over the long haul and makes replication much easier to manage....More
Red restore key on computer keyboard
Jun 24, 2014
blog

AlwaysOn Availability Groups and Third Party Log Readers

When DBAs and SysAdmins learn the ins-and-outs of AlwaysOn Availability Groups, they’re then able to address high availability and disaster recovery concerns from a single interface or set of tooling, thus providing better scalability of management....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) ×