CHAPTER 2 n MAKING DATABASE BACKUPS 32
Figure 2-7. A striped backup configuration: the backup is split into pieces among the
various backup devices.
Striped backups are too easy to create, in my opinion:
BACKUP DATABASE AdventureWorks
TO DISK ='D:\data\AW.bak',
E:\data\AW.bak',
'F:\data\AW.bak' WITH INIT,
CHECKSUM,
CONTINUE_ON_ERROR
In this particular example, the backup is being spread across all three files. Since
striping is above all a performance optimization, this example would have little impact
on performance if D:, E:, and F: were all on the same data array.
One of the most common mistakes I??™ve encountered is when a GUI-centric DBA creates
a striped backup by mistake. It??™s easy to do, and I??™ve accidentally done it myself (yet
another reason to move from using SQL Server??™s GUI interface to T-SQL whenever possible).
Here??™s what happens: a junior DBA begins his or her journey down the wrong path
by looking at the dialog shown in Figure 2-8.
CHAPTER 2 n MAKING DATABASE BACKUPS 33
Figure 2-8. Into which file will SQL Server place the backup? (Hint:What you ???see??? may not
be what you get.
Pages:
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108