How to fix Error 824 in SQL Server Database?

FIn this blog post, let us know the simple methods to fix error 824 in SQL Server Database.

Many of the users might have encountered this error and were not able to access the server’s MDF and NDF files. This error also disallows users to access the objects stored in the database. Thereby making it very necessary for the one encountering the error 824 to fix this on an immediate basis.

So, without wasting any more time, let us move ahead and read about the detailed symptoms and 

Know about SQL Database Error 824: Symptom, Description, and Causes

Symptom:

Msg 824, Level 24, State 2, Line 1.

Description:

The SQL Database error 824 is a logical Input/Output (I/O) error which implies that the page is successfully read from the disk. However, there’s an error on the page itself. 

Whereas, a ‘logical consistency error’ is a clear indication of damage in the SQL database due to the corruption in  I/O subsystem component 

If you wish to understand the error and know the various implications of this error, then these are:

• The file belongs to which database
• Whether the operation was read or write
• The I/O operation was performed against which database file in the MS SQL server.
• The I/O operation was related to which page number
• Complete information about the failed logical consistency check  i.e the actual and expected value used for checking, the category of checking, etc.)

Causes of SQL Database error 824

For the smooth functioning of I/O operations, Microsoft SQL Server uses Windows API’s, such as ReadFile, WriteFile, ReadFileScatter, and WriteFileGather. After executing the I/O operations, the server checks for errors related to these API calls. If the API calls that have been stated here fail with an Operating System error, then the SQL Server reports the error 823. There are circumstances when the ‘Windows API call’ is successful but the data moved by the I/O operation has met with logical consistency issues. 

Some of the other causes for the occurrence of SQL database error 824 are:

• Problems in the underlying storage system
• Hardware or driver issue in the I/O path
• Corruption in SQL Server database MDF or NDF file
• Probable discrepancies in the SQL’s file system

Method to Fix Error 824 in SQL Server Database

Now you need to check the suspect_pages table in msdb to check if other pages in the same database or different databases are encountering this error.

• You can use the built-in DBCC CHECKDB command to check the reliability of the databases that are located in the same volume (as the one stated in the 824 messages).

If you find issues on using this command, then troubleshoot the reported database consistency errors before moving further.

• Switch on the PAGE_VERIFY CHECKSUM database option in the database as soon as possible.
• You can now use the SQLIOSim utility to check if the SQL 824 error can be replicated outside of regular I/O requests in SQL Server.

Note – The 2008 version of SQL Server comes with this utility. If you have another SQL version, you need to download it from the official website.

1. You also need to work with the vendor of your hardware or device manufacturer to ensure the following points:
   • The ‘device drivers’ and other ‘supporting software components’ of all devices in the I/O path are updated and working properly.
   • The hardware devices and their configuration are in accordance with the I/O requirements of SQL Server.
2. If the hardware vendor or device manufacturer has provided you with diagnostic utilities, you should use them to assess if the I/O system is in working condition or not.
3. Confirm if there are ‘Filter Drivers’ existing in the path of I/O requests that face issues. To do so, check the following:
   • If there is any update available for these ‘filter drivers.’
   • Know if the ‘filter drivers’ be disabled or removed to resolve the SQL error 824.

With the use of the above-mentioned solutions, you can troubleshoot SQL error 824. However, there are some disadvantages to these methods. All of these methods are manual, are lengthy and are also time-consuming. Plus, they involve the risk of data loss and as well as failure due to a lack of technical expertise. All these factors make it really difficult for users to try out these manual methods on their own.

Alternate Solution

So, I would suggest you use the MS SQL Recovery Tool. This tool can help to resolve this error in no time and provides other benefits also. You can easily recover ‘deleted table records’ from the SQL Server along with objects, such as tables, triggers, keys, rules, indexes, defaults, etc. This tool supports all the older and latest versions of SQL Server such as 2017, 2016are, 2014, 2012, 2008, etc.

Conclusion

I have discussed the various manual techniques to fix Error 824 in SQL Server Database. You can try implementing these techniques to resolve these errors. Or you can use the professional MS SQL Recovery Tool to do the job easily. 

Related Post