Notifications
Clear all
Topic starter
I had noticed some strange errors popping up in my Centricity database's SQL logs, so I went to investigate. After a bit of poking around, I ran a "DBCC CheckDB WITH NO_INFOMSGS" against the CentrictyPM database in MS SQL 2008 R2. The results came back with 57 consistency errors. After some investigation, it seems like the best option to fix these would be to restore from a backup. The problem is that I'm almost certain that we won't have backups that go far enough back to correct the data.I could run a repair using DBCC but I'm afraid of the outcome. I'd obviously need to back up the database before running anything like that, but I wanted to run it by here first. Is there anything else I should check or consider before moving forward?
CHECKDB found 0 allocation errors and 56 consistency errors in table 'FMYCOVSTEPMEDDETAIL' (object ID 247526369).
CHECKDB found 0 allocation errors and 57 consistency errors in database 'CentricityPM'.
Posted : August 10, 2016 4:26 am
Hey drop me an email I have a good reference I can give you. My email is in my forum profile.
Posted : August 11, 2016 10:27 am
This is unfortunate as it does indicate you have corruption in the database. The out of the box options in SQL Server will almost certainly delete data.
Backups are the best option to remove the corruption; however, you want to see if you can identify what caused it. It could be on the application side--perhaps a load has gone bad or it could be on the hardware side. If it is the hardware, you will want to start taking steps to replace it.
Posted : August 25, 2016 9:39 am
