Every time the
VERIFYONLY command finds a suspect page, it will add a row to the SUSPECT_PAGE table, up
to a maximum of 1,000 times. If a single backup file produces in excess of 1,000 suspect
pages, then you have a serious problem to solve, and there??™s little point??”or so SQL
Server??™s designers believe??”in continuing to record errors.
Restoring Data Pages
New with SQL Server 2005, you can replace individual data pages with the RESTORE command.
You can do this either in offline or online mode. You would use online mode if you
discover a suspect page during normal operations. In order to have any level of success
with the page-level restore, the database must be in Full Recovery mode. Bulk-Logged
Recovery mode may work, but for practical purposes, don??™t count on page restores working
in that mode.
You can restore only actual data pages. This technique won??™t work for pages in log
files, nor for Global Allocation Map (GAM) pages, Secondary Global Allocation Map
(SGAM) pages, or Page Free Space (PFS) pages. Only data pages associated with a specific
table or index will work.
Pages:
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156