OrderHistory and its indexes
amount to 2GB in size. You could perform a full backup amounting to a little more than
2GB in size, or, as shown in Figure 4-8, you could restructure the database so that Order,
the indexes on Order, and OrderHistory are all on separate filegroups, with the
OrderHistory table??™s filegroup marked as read-only.
CHAPTER 4 n BACKING UP AND RESTORING FILES AND FILEGROUPS 92
Figure 4-8. An optimal filegroup configuration for using partial backups
Doesn??™t it make more sense to only back up the filegroups used for current order data
and indexes on an ongoing basis? Backing up the historical order data only once, instead
of many times over, saves backup time and storage space.
To restore from a partial backup, the syntax is fairly intuitive when compared with
the partial backup:
RESTORE DATABASE Adventureworks
READ_WRITE_FILEGROUPS
FROM DISK='C:\AWPartial.bak'
WITH PARTIAL, NORECOVERY
This RESTORE DATABASE command replaces only the read/write filegroups from the
backup file (and since that??™s all you backed up with the partial backup, there isn??™t anything
else to include).
Pages:
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200