Often the task is what I consider a low frequency / high liability event – something the typical DBA might only do once or twice in their career, but if called upon would be highly critical to the business.
For example (and one used by Russ in a presentation I saw once) let’s say that the drive that holds tempdb for your instance is gone. Someone made a change on the SAN and poof. Gone. So what do you do? How do you fix it? Do you panic? Or, just maybe, you’ve tried it before. You may not remember exactly what to do, but you know it can be done. A quick bit of memory searching (or as I call my memory Google) and off you go. Also likely the challenge is just a suggestion to push you to try something new.
Anyway, to make a long story short (Too late!) Russ has decided to retire the challenge and asked if anyone wanted to take it over. So, you guessed it, I’m going to give it a shot. I’m going to put my own spin on it though and it’s going to be SQL Homework. Get it? It fits the theme? Come on! It’s pretty obvious. Right? I’m going to be starting with basic but important tasks and I’ll do my best to build over time.
- June 2018 – Alter a database
- May 2018 – Create a database
- April 2018 – Indexes
- March 2018 – Recovery Objectives
- February 2018 – Work with security
- January 2018 – Inspect an Execution Plan
- December 2017 – View the log
- November 2017 – Create a view
- October 2017 – Download and attach/restore one or more sample databases
- September 2017 – Create a home lab
- August 2017 – Create a table
- July 2017 – Take a backup