??? User: Although point-in-time restores can bring you up to the point of a user error
(assuming that point is known), all data after the user error is lost.
Caveats and Recommendations
The following items are some things to keep in mind now that you??™ve read this chapter.
Keep them in mind, and your next restore will (hopefully!) be smooth and uneventful.
CHAPTER 3 n RESTORING A DATABASE 72
??? Use checksum instead of torn-page detection: Checksum validation is much more
thorough than torn-page detection. Yes, torn-page detection is less of a resource
drain, but it??™s a primitive technique for spotting corruption; it??™s possible to have a
complete, yet damaged, page.
??? Always specify a recovery clause when performing a restore: The default of bringing
the database back online via recovery has tripped me up in the past. If you
accidentally recover the database before restoring all the necessary files, you??™ll
have to start the process over. If the full backup is of any significant size, this will
result in a lot of downtime and frustration. Try to get in the habit of specifying
the WITH RECOVERY clause even when you??™re ready to recover the database.
Pages:
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171