YOUR CHANNEL IS LOADING

LATEST EPISODES MORE EPISODES

  • 1

    A Break from Data

  • 2

    Making New Infrastructure Investments

  • 3

    Use Tools

  • 4

    The TCO of the Cloud

  • 5

    Continuous Releases

The Voice of the DBA Stop, Don't Panic

MEVIOtoday

Mar 15, 2010 Stop, Don't Panic

What do you do if you come in and a database is suspect? What about you come in and someone else has already started a restore of the production database from midnight? What if any number of failures or actions have occurred, what do you do?

First you figure out what has happened and what is happening. You don't take any actions, and I'd argue that you might not even want to stop what's occurring. Someone might have a great reason for starting that restore, so don't stop it for now. Besides, the database has already been whacked at this point. Stopping the restore doesn't help you.

Read the rest of "Stop, Don't Panic" at SQLServerCentral.