??? Recovery is not possible due to damaged log files.
??? Recovery is not possible due to a break in the LSN chain.
Essentially, SQL Server prevents you from accessing the database because it can??™t
ensure consistent data. SUSPECT status is actually a good thing. It prevents you from proceeding
with potentially inconsistent data. The operative word here is potentially. In the
majority of the cases I??™ve dealt with, the problem had nothing to do with inconsistent
data, and a restore was not required. The single biggest issue with SUSPECT mode is that it
generates panic and a ???just get the system back up??? mentality, without regard to data loss.
Usually, the true cause for data corruption (such as hardware failure or damaged disk
drives) shows its ugly head well before a database moves into SUSPECT mode. If you??™re validating
your backup files before writing them to a tape drive, you should also discover a
problem before the database moves into SUSPECT status (if torn-page detection or checksum
verification is enabled).
SQL Server 2005 and higher supports an emergency startup mode.
Pages:
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168