It is true that the name is rather verbose, but there??™s a benefit from
that verbosity.
Depending on your environment, you may choose to use a naming convention that
does not explicitly differentiate a snapshot from a normal database. Why might you do
that? A snapshot is sort of a ???database view.??? In many systems, views are named in a manner
that the consumer of that information does not realize it is not a physical table, either
for pragmatic or security purposes. Database snapshots could be used in a similar fashion.
Using the example in the previous paragraph, perhaps simply Year2008Start would
be sufficient, and preferable, if the snapshot is to be exposed to users for writing ad hoc
queries or reports.
As with any naming convention, the key to success is to simply pick a naming convention
and stick to it. Having multiple naming conventions for different uses can
quickly lead to confusion.
Linking a Snapshot to Its Database
If you have the unlucky and unhappy reality of having existing database snapshots that
are poorly named, use this handy query that returns each database name and all of its
associated snapshots:
USE master
SELECT s1.
Pages:
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436