Resolve fatal error 823 from SQL Server Database

Have you encountered the fatal error 823 SQL while accessing the SQL Server Database or the numerous inconsistency errors while querying SQL Server Database? Such errors crop up when the SQL Server database is damaged or is inconsistent. You may encounter an error message like the following:

"2010-03-06 22:41:19.55 spid58 Error: 823, Severity: 24, State: 2. 2010-03-06 22:41:19.55 spid58”

Such an error is encountered in Windows Application Event Log or MS SQL ERRORLOG when you are performing any operation on the MDF of the SQL Server. This error can be fixed easily but if you have a clean and updated backup, then you can rest assure that no data will be lost. However, if you do not possess a current and updated backup then you can make use of an efficient and reliable tool that is designed and created for fixing issues like the one you have encountered.

Fatal error 823 occurred on the system because of the following reasons.

  • The SQL Server database and the MDF file are corrupt.
  • There is inconsistency in the file system, which means that there are I / O errors in the database.

To resolve the error you need to follow the steps given below to repair the MSSQL database files or to restore the SQL database.

  • To check inconsistency in the file system you need to run the Chkdsk and find out if there are any inconsistency issues that need to be resolved at the earliest
  • To repair the MSSQL Database you need to use the DBCC CHECKDB command and thus, repair the damaged MDF files in the SQL Server database.