Relying
on default behavior can be costly.
??? Don??™t rush into a restore of any kind: Stop. Breathe. Gather yourself before leaping
into action. Map out a plan of action on a piece of scratch paper before starting
anything (this is different than simply following the instructions of a prewritten
disaster recovery plan). If possible, ask a colleague to double-check your work.
DBAs, business users, or management almost always approach a restore situation
with a sense of urgency. There is a fine line between urgency and panic; rushing to
begin the restore process may create the momentum that carries you over that line.
??? Finding a database in SUSPECT status isn??™t the end of the world: While a database in
SUSPECT status could indicate a serious problem, it may just have a file in the wrong
location.
??? Be careful with the SUSPECT_PAGE table and page-level restore: That table only holds
1,000 rows, and it needs to be cleaned out manually. You may want to empty it on a
regular basis. Also, keep in mind that the SUSPECT_PAGE table holds information for
all databases on the instance.
Pages:
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172