Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Consistency Errors in CentricityPM MSSQL Database

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

3 Posts

3 Users

0 Reactions

64 Views

RSS

SLHV

(@slhv)

Posts: 478

Honorable Member

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

Marketing Committee

(@marketing_committee)

Posts: 358

Reputable Member

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

carlosjr

(@carlosjr)

Posts: 10

Active Member

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

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0