The other checksum-validation option is to CONTINUE_ON_ERROR. When this is enabled,
the backup simply writes the error to the MSDB..SUSPECT_PAGE table and continues on.
However, the SUSPECT_PAGE table has a limit of 1,000 rows, and if that is reached, the
backup will fail.
Enabling checksum validation obviously has a performance impact on your backup
process. If you have the luxury of a large maintenance window, checksum validation can
CHAPTER 2 n MAKING DATABASE BACKUPS 31
save you a lot of time and misery by avoiding the need to deal with a partially corrupted
backup file.
I??™ll examine the MSDB..SUSPECT_PAGE table and approaches to dealing with errors generated
by either torn-page validation or checksum validation in detail in Chapter 3.
Securing Backups
The BACKUP DATABASE and BACKUP LOG statements support a PASSWORD property:
BACKUP DATABASE AdventureWorks
TO DISK = 'D:\data\AW.bak'
WITH PASSWORD='monona'
This password is not strongly stored with the backup, and any hacker worth his salt
can break it. It is intended more to prevent the accidental restore of an incorrect backup
set.
Pages:
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106