All of that took time, and I had a deadline to meet within
three hours. I ended up missing the deadline (I did give my client a heads-up that the
data would be late that day), and ultimately this ended up being the last project I did with
that client. They weren??™t happy, and I completely understand why.
What Went Wrong
It was late at night, I was facing a deadline, and I just got sloppy. There??™s no other explanation.
I didn??™t take the time to perform a backup after I loaded the data (again, I was
concerned with the deadline), and my scripts didn??™t incorporate any sort of confirmation
step. This is a classic process disaster??”essentially, a user error for a planned activity.
Had I taken more care in double-checking my work, or had I taken the time to back
up the database after the load, I wouldn??™t have been in that position. It was a painful lesson
to learn, but things like this happen.
CHAPTER 11 n DISASTER RECOVERY PLANNING 288
How SQL Server 2005 Would Have Helped
Ah, if I only had SQL Server 2005. Database snapshots are the ultimate tool when it
comes to protecting against process disasters.
Pages:
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537