June 19, 2018 at 12:02 am
Comments posted to this topic are about the item SQL Server Database Corruption Detect
June 19, 2018 at 7:33 am
Actually, I had a bad page on disk. And CheckDB didn't detect the issue and when I restored the database it still shows the error. I ended up loading the table from my AlwaysON secondary node to the primary node and dropping the original table.
June 19, 2018 at 9:37 am
keeyu2 - Tuesday, June 19, 2018 7:33 AMActually, I had a bad page on disk. And CheckDB didn't detect the issue and when I restored the database it still shows the error. I ended up loading the table from my AlwaysON secondary node to the primary node and dropping the original table.
I am sorry to hear this. DBCC CHECKDB does not grantee finding all type of corruptions :(.
In your case, it probably had been there for a while since your backup was bad too.
I was helping on a situation recently. Both primary and secondary were corrupted. End up with creating the DB from scratch. The only good thing was that the DB was still up and running so we could dump data.
I guess we only can do as much as we can.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy