July 31, 2018 at 1:46 pm
My results of DBCC CHECKDB (SL_Forms) WITH NO_INFOMSGS, ALL_ERRORMSGS are:
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB
How do I do the repair_allow_data_loss?
July 31, 2018 at 1:53 pm
Please don't post multiple threads for the same problem.
No replies here please. replies to https://www.sqlservercentral.com/Forums/1979641/SQL-Server-detected-a-logical-consistencybased-IO-error
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 31, 2018 at 2:02 pm
If you are using DBCC CHECKDB you should have no trouble looking up the syntax for adding REPAIR_ALLOW_DATA_LOSS.
And while you're at it, do some research on what might go wrong, why you should do a full backup first, and all the implications of running it. If you can figure out what kind of pages are corrupt you might save yourself some trouble. If it is an index page, and you know what index, you might be able to fix the error by rebuilding the index. If it is a data page, you might want to dig deeper and figure out what rows of the table are at risk.
If you just blindly run that command on a critical database with no way to recover, you're taking a big gamble.
July 31, 2018 at 2:18 pm
GilaMonster - Tuesday, July 31, 2018 1:53 PMPlease don't post multiple threads for the same problem.No replies here please. replies to https://www.sqlservercentral.com/Forums/1979641/SQL-Server-detected-a-logical-consistencybased-IO-error
After I posted my long error message, it would no longer let me open the thread. I kept getting an error message on Chrome to wait or kill the page. Hit wait 5 times, reloaded the page, and did it again. Sorry for making another post.
July 31, 2018 at 2:19 pm
Scott Coleman - Tuesday, July 31, 2018 2:02 PMIf it is an index page, and you know what index, you might be able to fix the error by rebuilding the index. If it is a data page, you might want to dig deeper and figure out what rows of the table are at risk.
It's not an index page (minimum level would be repair rebuild if it was). On the referenced thread, it's about 1600 data pages.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply