By using frequent differential backups, you ensure that a minimal amount of files
are required to return the database to operational status. You should continue to have
frequent full backups (nightly is a minimum); otherwise, the size of each differential
backup will continue to grow to a potentially unwieldy size. You should time log backups
so that no more than one or two, plus the backup of the log??™s tail, are required for
restore. Here??™s a possible schedule:
??? Full backup nightly (starting at 10 p.m.)
??? Hourly differential backups during active usage periods (perhaps 7 a.m. to 7 p.m.)
??? Hourly transaction log backups, at 30 minutes past the hour during active system
usage
If data loss is acceptable, you could perform a full backup nightly and differential
backups every 30 minutes while leaving the database in Simple Recovery mode. This
eliminates the need for the possible backup of the log??™s tail as well as any transaction
log backups. If fast restore is truly the requirement, some level of data loss might be
acceptable.
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 129
IMPERSONATION AND BACKUP OPTIMIZATION
SQL Server 2005 allows impersonation from one database to another on the same server via the
TRUSTWORTHY database property, the AUTHENTICATE permission, and the EXECUTE AS clause.
Pages:
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263