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

PSA: CPS upgrades remove default column values on custom tables

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

84 Views

RSS

justinbelcher

(@justinbelcher)

Posts: 130

Estimable Member

Topic starter

If you have custom tables in your database, and those tables have columns with a default value, the default value will get cleared when you do a CPS upgrade. If you have routines or INSERT statements that depend on the default column values, those routines or statements will fail. This happened to us when upgrading from CPS 10 -> 12.0.9, and from CPS 12.0.9 -> SP 11.
Here are some SQL routines that you can use to minimize the pain.
Run this before and after your upgrade and compare the difference in output to determine which default values were dropped:
SELECT SO.NAME AS "Table Name", SC.NAME AS "Column Name", SM.TEXT AS "Default Value"
FROM dbo.sysobjects SO INNER JOIN dbo.syscolumns SC ON SO.id = SC.id
LEFT JOIN dbo.syscomments SM ON SC.cdefault = SM.id
WHERE SO.xtype = 'U'
AND SM.TEXT IS NOT NULL
ORDER BY SO.[name], SC.colid

Use a statement like this to recreate a default column value. You can make one sql file and recreate all dropped values at once:
ALTER TABLE cusMyCustomTable ADD DEFAULT (getdate()) FOR MyDatetimeColumn
ALTER TABLE cusMyCustomTable ADD DEFAULT ((0)) FOR MyBooleanColumn

Posted : December 29, 2015 7:47 am

Marketing Committee

(@marketing_committee)

Posts: 358

Reputable Member

Thanks for the PSA I hadn't heard this or seen it but I'll keep an eye out. For the most part I've moved any custom tables into their own databases. That way you don't have to worry about stuff like this.

Posted : January 4, 2016 5:38 pm

Share:

24 Forums
9,942 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