You’re responsible for making sure the database server doesn’t go down and that you don’t lose data.
You’ve been taking SQL Server full and log backups for a couple of years now, and you’ve even done a few successful restores when your butt was on the line. But now that you’ve decided to become a professional database administrator, you’re wondering what kinds of restoration problems you’re going to run into in the future. Are there patterns and practices that a Senior DBA would have taught you – if you were lucky enough to work alongside one? And if you need to run backups and CHECKDB more often, how can you make ’em run faster?
I want to help. I’m Brent Ozar, and I’ve worked with a lot of shops whose nightly maintenance tasks spiraled out of control. From long backups to corrupt restores to dropped tables, you’ll learn the kinds of server emergencies that have brought DBAs to their knees. I’ll show you how to prevent emergencies before they strike.
Why I Want to Present This Session:
Most servers I see have the same basic setup: full backups every day, log backups every hour, CHECKDB every week. Nobody thinks about how easy it would be to lose less data – until it’s way too late. Let’s start thinking about it now.
Latest posts by Brent Ozar (see all)
- What to Do When SQL Server is Unusually Slow - February 25, 2018
- Getting Better Query Plans by Improving SQL’s Estimates - February 25, 2018
- How Often Should You Run Backups and CHECKDB? - February 25, 2018