Soon i will be upgrading my EMR/Oracle system.
Currently on 9.8 SP12 on Windows Server 2008 R2.
My test system... (that we bailed on b/c of too many issues) is 9.10 on Windows Server 2008 R2.
I see in the config guide that 9.8 supports Server 2012 as of November 2013, but doesn't mention R2.
My ideal plan is to rebuild my (bigger) test system as Windows server 2012 R2, install 9.8 SP12, move my data over, change all URLs, etc. then upgrade the EMR in place on the new server. Leaving the old one in place in case we need to rollback.
Does anyone know if EMR 9.8 SP12 will install on Windows 2012 R2?
Alternatively, looks like i will have to upgrade EMR in place to at least 9.10 then move the data to the 2012 r2 server, which i hate (even though we are on VM and can do snapshots etc.)
Also in you want to compare notes on things (URLs, etc) you have to change when moving to a new server i would love to compare notes so I have my bases covered.
thanks,
peter
What EMR version are you planning on upgrading to?
Batman
9.12.3
My preference is upgrading on a temp server with the same OS as production (2008r2). Once the upgrade is complete copy the DB to it's final resting stop which would be 2012r2. This keeps your original production server intact if you need to fall back due to a failed upgrade. The only downside to this is it takes a little long overall as you're copying the DB twice. Small price to pay knowing I won't have a messy recovery in case the upgrade goes sideways.
Since you're on 9.8.12 you don't have to mess with 9.10. You can upgrade directly to 9.12.3 and it has all the 9.10 scripts built into it.
If you need more info you know where to find me. 🙂
Batman
541-610-2746
Thanks Brad. That is the way I started thinking.
In my real world consulting I’ve tried to take shortcuts (or been forced to) installing into an unsupported OS and would up in panic situations with copying dlls, etc to get stuff to work before upgrading.
With the flexibility of virtual machines, really no reason to go through that pain.
Now just testing, documenting steps, and getting the updates to urls and ip addresses down.
The hard one on this one in this upgrade is forcing people to use the history forms and new prescription forms. At least we weren’t early adopters!!!