How to Resolve MS SQL Error 824?

Lincoln Burrows ~ Modified: July 30th, 2015 ~ ~ 1 Minute Reading

This topic has 4 replies, 3 voices, and was last updated 8 years ago by Stephen West.

Viewing 5 posts - 1 through 5 (of 5 total)

Author

Posts
July 30, 2015 at 12:51 pm #405 Score: 0

Lincoln Burrows
Moderator

Karma: 16 pts

I got this error message, when I run SQL : select * from mydb.dbo.mytable,

Msg 824:
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2412; actual 0:0). It occurred during a read of page (1:2412) in database ID 5 at offset 0x000000012d8000 in file ‘mydatabase.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB).

I don’t have clean backup. how to fix this error message?

July 31, 2015 at 12:31 pm #407 Score: 0

Stephen West
Moderator

Karma: 4 pts

Run the Following Command:
DBCC CheckDB(<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS, TABLOCK

September 2, 2015 at 9:52 am #549 Score: 0
Andrew Jackson
Moderator

Karma: 1 pt
Try this:
```
ALTER DATABASE corrupted_db SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC ChECKDB ('corrupted_db', REPAIR_ALLOW_DATA_LOSS) 
ALTER DATABASE corrupted_db SET MULTI_USER
```
but there is very high chance of data loss
April 5, 2016 at 12:28 pm #1831 Score: 0

Lincoln Burrows
Moderator

Karma: 16 pts

After a long search on google I have found this article please go this one it may be helpful to you. You can easily troubleshoot the error 824 easily. http://sqltechtips.blogspot.in/2015/11/troubleshooting-error-824.html

April 27, 2016 at 9:56 am #1987 Score: 0

Stephen West
Moderator

Karma: 4 pts

Typically the leading cause of corruption is problems with the IO subsystem.
Author

Posts

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.