- 论坛徽章:
- 1
|
alter 错误,请指教,急~~
1 Check the server error log for other errors that may have been raised prior
to the 692 error. Save the entire error log.
2 Obtain page information by running dbcc page as soon as possible, using
the database ID and page number shown in the message:
1>; dbcc page (<db_id>;, <page_number>;, 0, 1, 1, -1)
2>; go
3 Identify the object named in the error message using the following isql
commands:
1>; use <database name>;
2>; go
1>; select name from sysobjects where id=<object_id>;
2>; go
4 Find information about this object in sysindexes:
1>; select first, root, doampg, ioampg from sysindexes
2>; where name = object_name(<object_id>
3>; go
5 To determine the full extent of the corruption, run dbcc checkstorage, the
dbcc checkdb and dbcc checkalloc commands, or dbcc checktable and dbcc
tablealloc) as soon as possible.
6 To check if this error is a result of hardware failure, examine your
operating system error log and correct hardware problems. See “Checking
the Operating System Error Log” in the Encyclopedia of Tasks chapter for
assistance. |
|