Table 5-5. Risk Breakdown for a Specific-Tables-Only Scenario
Risk Worst-Case Impact Best-Case Impact
Data loss All Order and Order Detail information Zero data loss
Restore time Dependent on the number of trans- Dependent on the number of trans-
action log restores required action log restores required
Perceived If a full database reconstruction is If portions of the database are usable
downtime necessary, could be much longer than without these two tables, possible to
just restoring data (due to the need to have partial availability
load seed information and such)
Scenario: Large Full-Text Catalogs
Since full-text catalogs are now included with a full backup, you may need to separate the
backup of the database and the backup of the full-text catalogs. The inclusion of full-text
catalogs in full backups is new behavior in SQL Server 2005, and business units need to
be aware of it.
Requirements
The application in question relies heavily on full-text indexes, so ensuring that they??™re
backed up is critical. In fact, the bulk of the data used by the application is the full-text
catalogs, so without them, the system would be unusable.
Pages:
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276