with self

  do grenade.launch;


  on E:EFumble

  do Cover.Find(taFirstAvailable).Use;


 via +Ole Aass

Originally shared by Eliseo Arias

When teaching a junior developer how to use drop database.

6 thoughts on “try

  1. My boss did that once – accidentally dropped a production database on a client site. He noticed it before any users did, and restored from the backup he just made.

  2. Reminds me of a story I heard some years back from one of the people in the affected office. It happened in a quite sizeable company which I will not name.

    The company was upgrading internal computer systems. A special team had been created, which would travel from office to office, spending a month in each, backing up data, installing new systems and restoring the data. They set up shop in the office my friend was in, and began the operation. Part of the process was to make three backups to tape. These were created, duly labeled, and consigned to a safe place. The work proceeded, and when the time came to restore the data, they found that all three tapes were unrecoverable. (This, by the way, replicates my own experience with tape backups.) Apparently their protocol did not include verification of the backups. The fallback position was manual entry from paper records….

  3. Bill Meyer : I always heard that until you prove you can restore from backup, you don’t actually have a backup. There have been so many times that customers’ on site DBAs have ruined our backups in the name of “optimizing” and then never tested to see if it worked. Well never tested until the second drive in their RAID failed.

  4. Jim McKeeth That accords with my experience. In the time I did spend fiddling with backup tape, I found that perhaps 2/3 of the time, they would not verify, much less restore. RAID is a whole other issue. I love RAID, but never cease to be amazed at the number of people who do not understand  that although you can restore an entire drive, with two you lose the whole array. And the RAID 0 and 1 people are just silly.