Possible schema corruption. Run DBCC CHECKCATALOG.

[xuyiquan1981]

我们一个数据库坏了之后，通过恢复过来，用户连接和SQL自带备份基本正常。
但是在做DBCC checkdb检查一致性时报错如下：
Possible schema corruption. Run DBCC CHECKCATALOG. 在windows事件管理器里面也有，ID是211.
也就是无法做DBCC CheckDB。
另外一些错误提示：
An error occurred while executing the following query: "DBCC CHECKDB([DBName]) WITH PHYSICAL_ONLY".
On server: "ServerName".
SQL error number: "0000".
SQL error message: "".

An error occurred while executing the following query: "BACKUP DATABASE [DBName] TO virtual_device = 'sDBName_00__0cb8991e_80d1_4a62_a674_02d20ad097a4_' WITH name = 'Backup Exec SQL Server Agent'".
On server: "ServerName".
SQL error number: "0000".
SQL error message: "".

但是做DBCC CHECKCATALOG，没有报错，可以顺利完成。

不时会报如下错误：
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x56d779ae; actual: 0x7b1f88ed). It occurred during a read of page (4:54482) in database ID 9 at offset 0x0000001a9a4000 in file 'Q:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\DBName_index.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x33b62a4b; actual: 0xbd14b15d). It occurred during a read of page (4:21532) in database ID 9 at offset 0x0000000a838000 in file 'Q:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\DBName_index.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.


其中16进制会有变化（0x56d779ae，0x7b1f88ed，0x0000001a9a4000）

各位大侠，有什么方法检查吗？谢谢

[dawugui]

如果是这样,建议重建立数据库,然后把所有表,数据都全部导过去,把存储过程等内容都重建立.这样保险得多.

[xuyiquan1981]

[Quote=引用 1 楼 dawugui 的回复:]
如果是这样,建议重建立数据库,然后把所有表,数据都全部导过去,把存储过程等内容都重建立.这样保险得多.
[/Quote]

谢谢，请大家多给些意见，感激。。。。。

[bancxc]

[Quote=引用 2 楼 xuyiquan1981 的回复:]

引用 1 楼 dawugui 的回复:
如果是这样,建议重建立数据库,然后把所有表,数据都全部导过去,把存储过程等内容都重建立.这样保险得多.


谢谢，请大家多给些意见，感激。。。。。
[/Quote]数据小还可以考虑

[obuntu]

可以重建的话，就重建吧，安全又简单的方式。

不然里面的一些控制规则，只有微软才知道的。

[xuyiquan1981]

6GB数据，有没有一些检查方法？
Veritas还有一个提示：
Snapshot provider error (0xE0000353): The path for this database is invalid because it contains extra backslash characters. You must remove the extra backslash characters before the database can be backed up.

[xuyiquan1981]

没有人懂吗？

[xuyiquan1981]

顶。。。。。。。。