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

aPractice v20 - Windows 2012 & SQL 2016 SP2

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

8 Posts

3 Users

0 Reactions

98 Views

RSS

priddyjosh

(@priddyjosh)

Posts: 4

Active Member

Topic starter

Wanted to reach out to the community to see if anyone has any opinion or experience with the following scenario.

** As a note, I have already open a ticket with AH support and have been told that what is listed in the "Configuring Environments for Centricity Practice Solution v....." are the only platforms (Win\SQL) that the product has been "validated" at and that anything else may suffer in the areas of "system stability, performance, and data integrity".

Scenario:

We have an aPractice (CPS) 12.3.3 product running on Windows 2012 (non R2) JBoss with SQL at 2012 SP4. We are planning for an upgrade to aP v20 SP1 (coming soon!) after we first perform an in-place upgrade of SQL and take it to SQL 2016 SP2 (which is the min SQL version for v20).

Problem:

The config guide for v20 states that the min spec for Windows is Windows 2012 R2 and that the min SQL version is 2016 SP2. The maximum SQL spec for 12.3.x is 2016 SP1. There is only a one service pack (on the same version) difference between the min and max versions of SQL for the two aPractice versions being discussed.

Ideally we would like to have some confidence that the 12.3.x CPS product will not break if we go to SQL 2016 SP2 as well as some confidence that we could deploy v20 on a Windows 2012 (non R2) JBoss server. Has anyone stepped down this path and have any lessons learned or advice?

Thanks,

Josh Priddy

Posted : March 19, 2021 7:02 am

swestfisher

(@swestfisher)

Posts: 132

Estimable Member

Hi Josh,
We were in the LA group and are now live on v20. It is possible to run v12.3.x on Windows 2016 and SQL Svr 2016, this is what we did previous to upgrading to v20. The only tricky part is if you need to INSTALL v12.3 into a 2016 environment. If you do you have to disable the version check for the jBoss installer. We ran for over a month on 2016 terminal servers as well. We actually created new servers for the environment with 2016 (it was quicker for us than upgrading). Another LA user told me about the jBoss install "fix" and we were off and running.
Steve

Posted : March 19, 2021 7:24 am

priddyjosh

(@priddyjosh)

Posts: 4

Active Member

Topic starter

Thanks for taking the time to read and reply Steve. I guess I should of stated our goal here is to not spend the time and budget on building out a new environment but rather live on what we currently have (Windows 2012 (no R2) & upgrade SQL to 2016 SP2). The concerns we have are if there will be issues with CPS 12.3.x running on SQL 2016 SP2 while we work towards the v20 SP1 upgrade on Test & then Live and if v20 will run on Windows 2012 (no R2) servers.

Posted : March 19, 2021 7:41 am

swestfisher

(@swestfisher)

Posts: 132

Estimable Member

Hi Josh,
I may not have been clear. We did run CPS 12.3.x on 2016 R2 OS and 2016 SQL Server for about a month before we upgraded to v20. I just meant to say that we built a new 2016 environment and ran CPS 12.3.x on that rather than upgrading the existing 2012 environment to 2016. We also didn't have resources to build the entire environment out with 2016 and didn't have downtime to do the OS/SQL and v20 upgrade at the same time. So we upgraded sets of servers on different days - so the terminal servers one week, database servers another week, and jBoss servers another week. Then it was about one month before we were ready to upgrade to v20.
Steve

Posted : March 19, 2021 7:51 am

lic08

(@lic08)

Posts: 286

Reputable Member

we are currently on 12.3.3 and running sql 2016 on a windows 2012 r2 if that helps.

Posted : March 26, 2021 3:40 am

priddyjosh

(@priddyjosh)

Posts: 4

Active Member

Topic starter

That does help. Thank you for the review and response! ~ Josh

Posted : March 26, 2021 3:43 am

priddyjosh

(@priddyjosh)

Posts: 4

Active Member

Topic starter

Sorry, forgot to ask what specific version\service pack of SQL are you on? While 12.3.3 has been "validated" up to SQL 2016 SP1, we are looking to take it to at least SP2 in order to satisfy the minimum SQL requirement for v20. Thanks ~ Josh

Posted : March 26, 2021 4:23 am

lic08

(@lic08)

Posts: 286

Reputable Member

SP2

Posted : March 26, 2021 4:28 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