- 论坛徽章:
- 0
|
需要急救!!!前辈们帮忙看看!!!
或者这个也可以
You're in trouble (or rather, your database is). You're basically looking
at a corrupted transaction log. There's no easy way to fix this. Also, the
fact that this applies to sysindexes (object 2) is not good news. I've had
this problem (error 3474) once before, and the only thing we could do was
to get rid of the transaction log and build a new one (using dbcc
rebuild_log, which is a *very* heavy-handed approach that's only a
last-resort measure). However, as you have a problem with sysindexes, this
doesn't sound like a good idea, as it might leave sysindexes corrupted.
Also, there seems to be a lot of stuff in the log, given all the redo
messages. You'd loose these when rebuilding the log. I'd recommend to
first try to extract your data out of that database, build a new database,
and load the data there. To extract the data, update the status column in
sysdatabases to -32768 for your database and cycle the server. When it's
restarted, use BCP or 'select into' to move your data out of this
database. Then drop (or rename) the current database and create a new one. |
|