英中对照^^Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.Explanation Microsoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.Action Check the accessibility and condition of the device in question.Run hardware diagnostics and correct problems, if possible.Restore damaged files from the latest database backup. Restoring from a database backup should always be considered the primary means of fixing a damaged database. If you don't have a backup or if the errors detected are very isolated, the repair functionality of DBCC CHECKDB may be useful. However, using DBCC CHECKDB can be more time consuming than restoring the damaged files from a backup, and you may not be able to recover all your data .Caution If running DBCC CHECKDB with one of the repair clauses does not correct the problem or if you are unsure how this process may affect your data, contact your primary support provider.
DBCC CHECKDB
来修复试试
错误 823
严重级别 24
消息正文
在文件 ''%4!'' 的偏移量 %3! 处的 %2! 过程中，检测到 I/O 错误 %1!。解释
Microsoft® SQL Server™ 在对某设备进行读或写请求时遇到 I/O 错误。该错误通常表明磁盘问题。但是，错误日志中在错误 823 之前记录的其它核心消息应指出涉及了哪个设备。对策
检查该设备的可访问性和状态。如果可能，执行硬件诊断并纠正问题。从最新的数据库备份还原损坏的文件。从数据库备份中还原应始终是修复已损坏数据库的首选方法。如果没有备份或者检测到的错误是孤立的，则 DBCC CHECKDB 的修复功能可能很有用。然而，比起从备份中还原损坏的文件，可能使用 DBCC CHECKDB 消耗的时间更多，且可能无法恢复全部数据。注意 如果使用修复子句运行 DBCC CHECKDB 时，问题没有得到纠正，或者不知道该过程将如何影响数据，请与主要的支持提供者联系。
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.Explanation
Microsoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.Action
Check the accessibility and condition of the device in question.Run hardware diagnostics and correct problems, if possible.Restore damaged files from the latest database backup. Restoring from a database backup should always be considered the primary means of fixing a damaged database. If you don't have a backup or if the errors detected are very isolated, the repair functionality of DBCC CHECKDB may be useful. However, using DBCC CHECKDB can be more time consuming than restoring the damaged files from a backup, and you may not be able to recover all your data .Caution If running DBCC CHECKDB with one of the repair clauses does not correct the problem or if you are unsure how this process may affect your data, contact your primary support provider.