The file itself has a datetime stamp, so this is probably your
best choice if you don??™t need to remove the backup files programmatically.
??? DateTime_DatabaseName_BackupType (e.g., 0713051113_AdventureWorks_Full.bak): This
technique is usually used when custom scripts maintain the backup history.
??? DatabaseName_BackupType_ExpiryDateTime (e.g., AdventureWorks_Full_091305.bak):
If someone needs to create a backup out of the regular backup schedule, this format
allows you to programmatically remove the files that are no longer needed.
??? DatabaseName_BackupType_BackupReason (e.g., AdventureWorks_Full_PreUpgrade.bak):
This naming convention is similar to the previous one in that it represents a
backup created out of the regular backup schedule. I find this technique more useful
than the previous one because it describes the reason for the backup, not just
when you can delete it.
??? DatabaseName_BackupType_3rd-PartyFormat (e.g., AdventureWorks_Full_<
application name>>.bak): If you use a third-party application to create backups for
compression or encryption reasons, it??™s nice to see the name of the application (or
an abbreviation) in the name of the backup file.
Pages:
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86