com/en-us/library/ms130214.aspx) will do nicely.
As you read, you may find yourself disagreeing with a recommendation I make or
my technical description of some process. Excellent! If you disagree with me, that shows
you??™re thinking about disaster recovery. I??™m happy with you disagreeing with my book as
long as you have your own approach to disaster recovery.
One other item about this book: the term best practices is deliberately absent. I speak
at a number of SQL Server conferences, and I attend Microsoft Tech???Ed every year??”in
other words, I see lots of presentations. However, I seldom hear specific ideas about what
to do with a particular technology, other than a slide or two talking about best practices.
The truth of the matter is, there is no such thing as a best practice; every situation is different,
and what can be a good idea in one environment can lead to bedlam in another.
xxi
Who This Book Is For
If you??™re a database administrator, either by choice or by necessity, understanding disaster
recovery should be at the top of your to-do list. The problem is that disaster recovery
is often either seen as a complicated, expensive process or it is minimized to the role of
a basic backup/recovery plan.
Pages:
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46