Message 823 - Is it physical fault?
Grzegorz Gruza
sometimes during running SQL queries I receive an message 823
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
Does this error point on physical fault on my disk? If not, what should I do
for avoiding SQL Server errors?
Best regards,
--
Grzegorz Gruza
gr...@priv4.onet.pl
Erland Sommarskog
> sometimes during running SQL queries I receive an message 823
> I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
>
> Does this error point on physical fault on my disk? If not, what should I do
> for avoiding SQL Server errors?
For you convenience I have copied the text for error 823 from Books Online
below. Next you wonder about an error, search for the number in Books Online.
Many error codes have a write-up there. Many more does not, but it is always
a good idea to start in Books Online anyway.
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.
See Also
RESTORE
DBCC CHECKDB
Errors 1 - 999
--
Erland Sommarskog, Stockholm, som...@algonet.se