Keep these restrictions in mind as we continue. If you haven??™t already guessed it, they
have a profound impact on the practical usage of database snapshots.
Managing Database Snapshots
The use of database snapshots can be quite appealing; however, they carry a heavy management
burden. Even though you can create them only using a T-SQL script, they
appear in SSMS under a special Database Snapshots folder, as shown in Figure 9-4.
CHAPTER 9 n DATABASE SNAPSHOTS 234
Figure 9-4. All database snapshots, regardless of what database they point to, appear
together in the same Database Snapshots folder in SSMS.
Another potentially confusing aspect to the presentation of database snapshots in
SSMS is that once opened, they look exactly like any other database. Even viewing the
properties of a database snapshot gives the impression that you??™re looking at an actual
database. Figure 9-5 shows the problem.
Figure 9-5. Other than the Name property that I??™ve chosen (AdventureWorks_SS_1), nothing
indicates that this screen shows the properties of the database snapshot.
CHAPTER 9 n DATABASE SNAPSHOTS 235
If left unmanaged and only used marginally, database snapshots do little more than
consume disk space and clutter the Management Studio landscape.
Pages:
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433