It??™s late at night, and both consultants are
starting to get a little punchy. They commence updating pricing for one category of products
(there are more than 10 million products in the table). Consultant #1 issues the
command UPDATE PRODUCT SET PRICE=1*1.1 and executes the query. He immediately panics,
because he realizes he forgot to put a WHERE statement on the query. He proceeds to
flip out. Consultant #2 calmly walks over to the server and disconnects the power. When
the server comes back up, the database system rolls back the interrupted UPDATE
statement. All is well with the world.
This is an excellent example of a process disaster, and one we??™ve all experienced at
one time or another.
CHAPTER 11 n DISASTER RECOVERY PLANNING 287
The Scenario
This one is personal??”very personal. In fact, I??™m the subject of the story.
I was working on a massive data migration from one system to another, which meant
changes in data layout, data types, and so on. Every test took an extremely long time to
prep on the source side, to prep on the intermediary system, and to export from my system
to a format that I could load into the target system.
Pages:
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535