The troublesome thing about restoring is that it returns the database to that
point in time immediately. There??™s no ???snapping back.???
As with the DROP command, if you don??™t use a naming convention that identifies the
snapshot as a snapshot, it is possible to accidentally restore the wrong database, particularly
if you??™re writing the T-SQL statement on the fly. Just as I would write the word WHERE
before constructing a DELETE or UPDATE statement, I recommend writing the RESTORE statement
with FROM DATABASE_SNAPSHOT first.
A number of requirements must be met before you can restore a snapshot:
CHAPTER 9 n DATABASE SNAPSHOTS 233
??? There can be no other snapshots of the source database: You must delete all other
snapshots before reverting. Needless to say, be very certain you know which snapshot
you need if you maintain more than one on any given database.
??? All full-text catalogs must be dropped: Since full-text catalogs are still stored outside
of the database itself, reverting to a snapshot would invalidate any catalogs; fulltext
search would be unaware of the change in the database.
Pages:
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431