SQL Server 2005 runs
a much more thorough check of the database structure itself. This occurs even if the
page-verification option for the database is set to None.
When verifying a backup, you may want to include the clause CONTINUE_ON_ERROR
instead of the default STOP_ON_ERROR. This gives the operation a chance to complete
with the hope that only a handful of pages may be corrupted. Intuitively, this may
seem to be waste of time, but restoring a database that you know will ultimately be
incomplete can actually save time drastically. If, on the other hand, you go with the
default of STOP_ON_ERROR, you may be pausing to correct a problem only to have
another problem occur further in the restore process. You??™ll end up running longer
and longer portions of the restore process, finding each error one at a time. It??™s often
faster to choose CONTINUE_ON_ERROR and get a listing of all errors in one pass.
nNote You can even specify CONTINUE_ON_ERROR with regular BACKUP and RESTORE commands. You can
specify the clause regardless of whether you also specify VERIFYONLY.
CHAPTER 3 n RESTORING A DATABASE 63
If you let a verification process continue after an error, it will record the corrupted
pages to a new table in the MSDB database: the SUSPECT_PAGE table.
Pages:
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155