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

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Register Now and get your question answered!
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 MDF Corruption
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

1 Posts

Posted - 12/30/2009 :  03:24:00  Show Profile  Reply with Quote
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
This error message may occur every time when I start SQL Server and access the MDF file.

Thanks in advance.


Aged Yak Warrior

595 Posts

Posted - 12/30/2009 :  03:29:08  Show Profile  Send rajdaksha a Yahoo! Message  Reply with Quote

May be its useful


Go to Top of Page

Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 12/30/2009 :  03:54:39  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Please run the following and post the full output.


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

Starting Member

3 Posts

Posted - 01/18/2010 :  23:18:42  Show Profile  Visit sam.joseph74's Homepage  Reply with Quote
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.

<spam removed>

Edited by - tkizer on 01/18/2010 23:30:16
Go to Top of Page

Almighty SQL Goddess

38200 Posts

Posted - 01/18/2010 :  23:55:13  Show Profile  Visit tkizer's Homepage  Reply with 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

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
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000