Theme Graphic
Theme Graphic

SQL Database Recovery | Repair SQL Database

SQL recovery software to recover & repair corrupted MS SQL database from MSSQL Server. Support recovery of data from MS SQL 2000, 2005 &...

Subscribe

Author

I have completed my Ph.D in computer science and currently doing research on how to recover and repair corrupted database. During my research i found many third party software for several database recovery like sql recovery, sql repair, mdf recovery, mdf repair, db2 recovery, oracle recovery and many more. i am sharing my experience and knowledge with you all.

Archive

Open 2010

Tags

Posted on Sunday, June 13, 2010 at 11:28 PM

I/O Logical Check Failure Cause SQL Server Database Corruption


Like other databases and files, Microsoft SQL Server database may also come across various corruption issues. The corruption can take place due to various reasons, including the internal database or SQL Server application issues and system related problems. One major system related problem, which can cause MDF (Master Database File) corruption, is I/O logical check failure. In such situations, the database becomes totally inaccessible and you come across severe data loss situations. In order to get your mission critical data back, you need to repair and restore the corrupt database using SQL database recovery solutions.

The I/O logical check failure can be indicated by various error messages, which includes the following one:

“Error 823 I/O error <error> detected during <operation> at offset <offset> in file '<file>'”

The above error may also occur when SQL Server come across other system errors. After this behavior, SQL Server database become totally unusable. In order to sort out this problem, you need to fix it through SQL recovery methods.

Cause

If the read Windows API (Application Programing Interface) call or writer API call for SQL Server database is successful, but some particular logical checks are unsuccessful. In such cases, error 823 occurs, which resembles the following:

“2003-09-05 16:51:18.90 spid17 Error: 823, Severity: 24, State: 2 2003-09-05 16:51:18.90 spid17 I/O error (torn page) detected during read at offset 0x00000094004000 in file 'F:\SQLData\mydb.MDF'..”

Resolution

In order to work around this behavior of Microsoft SQL Server database and perform SQL Server recovery, you should first run DBCC CHECKDB utility on the affected or damaged MDF file. Before you try to fix any system related issue with MS SQL Server, you should first check the database and sort out the problems. If DBCC CHECKDB statement fails to detect or fix any error, please check the Application Event Log of Microsoft SQL Server.

If the above method fails to find and fix any errors in Microsoft SQL Server, you need to restore the database from a valid and recent backup to get your valuable data back. In case backup is not available, you have to opt for third-party applications to repair and restore the corrupted MDF file.

The repair mssql applications are particularly designed to methodically scan entire database and extract all inaccessible data from it. The software have read-only approach and simple graphical user interface to ensure safe and easy recovery.

Stellar Phoenix SQL Recovery is the most efficient and powerful utility to ensure absolute recovery in all MDF corruption situations. It works well with Microsoft SQL Server 2008, 2005, and 2000. The software restores all MDF file objects, such as tables, reports, forms, macros, stored procedures, and triggers.
Bookmark: Submit To Digg Submit To reddit Submit To del.icio.us Bookmark With StumbleUpon Bookmark With FaceBook Bookmark With Google Bookmarks   Share: Share By Email By Email

0 comments on "I/O Logical Check Failure Cause SQL Server Database Corruption"
No comments posted yet.

Leave A Comment
Subject:


Comment:
   Bold Italic Underline          Code Link Image Horizontal Rule


Because you do not have or are not logged in to your Programmer's Heaven account, please enter your name.

Name:


To help prevent comment SPAM, please enter the magic code '214' in the box:




Posting Rules
Please follow these rules when posting comments on blog posts.
  • Do not post anything that is racist, hate speech or of a sexual or adult nature.
  • Do not post or link to anything that infringes copyrighted laws.
  • Posting about security or legal topics is fine so long as you are not glorifying or encouraging people to perform illegal activities.
  • Both the author of this blog and the Programmer's Heaven administrators may delete any inappropriate comments without notice at their own discretion.
 

Recent Jobs

Official Programmer's Heaven Blogs
Web Hosting | Browser and Social Games | Gadgets

Popular resources on Programmersheaven.com
Assembly | Basic | C | C# | C++ | Delphi | Flash | Java | JavaScript | Pascal | Perl | PHP | Python | Ruby | Visual Basic
© Copyright 2011 Programmersheaven.com - All rights reserved.
Reproduction in whole or in part, in any form or medium without express written permission is prohibited.
Violators of this policy may be subject to legal action. Please read our Terms Of Use and Privacy Statement for more information.
Operated by CommunityHeaven, a BootstrapLabs company.