There are no automated
methods supplied for managing the database snapshots??”no automatic naming
convention or linking a database snapshot to its home database. Developing an effective
management routine for database snapshots should be a requirement before even considering
their use.
Applying a Naming Convention
I have seen, firsthand, extremely poor naming conventions for database snapshots. Even
the barely adequate naming schemes (as shown in Figure 9-4) leave questions about the
role of each individual database snapshot.
An appropriate naming convention should be able to answer the following questions
for any given snapshot:
??? What database does the snapshot point to? All database snapshots appear in the
same place in SSMS. Unless you??™re in luck and have only a single production database
on your SQL Server instance, including the name of the source database is
critical.
??? When was the snapshot created? Knowing the creation date of a database snapshot
is not an item of convenience for the DBA. A snapshot is a point-in-time view of an
entire database, so the creation date drives exactly what will be contained within
the snapshot.
Pages:
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434