Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 MDF Corruption

Author  Topic 

suehoege
Starting Member

1 Post

Posted - 2009-12-30 : 03:24:00
Hello everyone,

While writing to the SQL Server database, I might encounter the below error message:
“Error 823
I/O error <error> detected during <operation> at offset <offset> in file
'<file>'”
This error message may occur every time when I start SQL Server and access the MDF file.

Thanks in advance.

suehoege

rajdaksha
Aged Yak Warrior

595 Posts

Posted - 2009-12-30 : 03:29:08
Hi

May be its useful

Refer
http://support.microsoft.com/kb/828339

-------------------------
R...
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2009-12-30 : 03:54:39
Please run the following and post the full output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Also, check through the windows event logs and look for hardware-related (specifically IO related) errors

Do you have a backup of this database?


--
Gail Shaw
SQL Server MVP
Go to Top of Page

sam.joseph74
Starting Member

3 Posts

Posted - 2010-01-18 : 23:18:42
I am fully satisfied with Gail Shaw. Use DBCC CHECKDB command to check any logical errors in the database. It is an in-built command in SQL Server to fix application level errors. Else you have to use SQL Database Recovery software to scan the corrupted database and recover all the inaccessible data from it. These software are specifically designed to Repair SQL database in most of the corruption scenarios. I hope your problem will be resolved by using DBCC CHECKBD Command otherwise use Stellar Phoenix SQL Recovery Software.

Sam
<spam removed>
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-01-18 : 23:55:13
quote:
Originally posted by sam.joseph74

I am fully satisfied with Gail Shaw.



Me too, but your reply not so much. First DBCC CHECK does not fix *any* application level errors. It fixes only database level errors. Second I edited out your link as we consider it spam as it appears the sole purpose of responding to this topic was to include it.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page
   

- Advertisement -