Extreme Disaster Recovery
Here’s your chance to learn data recovery from the big dogs. Two Microsoft Certified Masters (MCMs) will take your Recovery game to an all new level. Take a deep dive into SQL Server recovery and learn how to handle a wide variety of data loss and corruption scenarios. The session will cover how to be prepared for, prevent, and recover data lost due to deletion or corruption.- Learn the following skills in this session:
- Built-in functionality in SQL Server for preventing and detecting corruption that you may not even know about
- How to identify a specific transaction in the transaction log and recover data lost from that transaction
- Categories of corruption and how to manage recovery differently for each one
![]()
Don’t come empty handed. Bring your laptops, and we’ll practice recovering corrupt databases together.
Register here for SQLBits and a Pre-con
Past Posts in the Series
If you missed any of the earlier posts in my DR series, you can check them out here:
- 31 Days of disaster Recovery
- Does DBCC Automatically Use Existing Snapshot?
- Protection From Restoring a Backup of a Contained Database
- Determining Files to Restore Database
- Back That Thang Up
- Dealing With Corruption in a Nonclustered Index
- Dealing With Corruption in Allocation Pages
- Writing SLAs for Disaster Recover
- Resolutions for All DBAs
- Use All the Checksums
- Monitoring for Corruption Errors
- Converting LSN Formats









Twitter
LinkedIn
TLF
RSS
WritersCafe
SQLPASS
Facebook
Pingback: Day 12 of 31 Days of Disaster Recovery: Extreme … – SQLSoldier « Quick Disaster Recovery.com
Congrats! Look forward to seeing you there.
You too! Too bad I can’t attend your pre-con or vice versa.
Pingback: Day 14 of 31 Days of Disaster Recovery: Fixing a Corrupt Tempdb | SQLSoldier
Pingback: Day 15 of 31 Days of Disaster Recovery: Running DBCC CheckTable in Parallel Jobs | SQLSoldier
Pingback: Day 22 of 31 Days of Disaster Recovery: Which DBCC CHECK Commands Update Last Known Good DBCC | SQLSoldier
Pingback: Day 26 of 31 Days of Disaster Recovery: The Mysterious Case of the Long Backup | SQLSoldier