Even if
they weren??™t sure what to do there, it would have prompted a phone call to me
much earlier. I??™ve run into this mistake in SQL Server 2000 systems regularly, and
the simple inclusion of a warning message can make all the difference in saving as
much data as possible.
??? Defaults: Knowing what the defaults are for any given operation is critical. With a
restore process, the default action is to recover the database??”that is, roll forward
the committed transactions and roll back the uncommitted ones. From that point
on, no further restore operations are possible. How could SQL Server 2005 have
helped with this? There are more functions in SQL Server 2005 that leverage the
ability to continually restore backup files. Log shipping and database mirroring are
the first that come to mind. Had SQL Server 2005 been implemented, the critical
nature of the WITH RECOVERY default would have been more apparent and would
have probably been stressed in the documentation.
CHAPTER 11 n DISASTER RECOVERY PLANNING 280
??? WITH COPY_ONLY: In SQL Server 2000, anytime a full backup is taken in the middle of
a standard backup scheme, all following differential backups are then associated
with that full backup.
Pages:
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519