Home Forums Discussions Problems SQL server 2012 to 2016

My local hosted AC has a 2012 SQL that is 32bit. I have not been able to upgrade to 2016. There were many different instructions when this was a thing. I just gave up at the time. I now would like to fix this. I now find out the problem is the 32bit SQL. I pay for support ever year. Is this something AC support is supposed to fix or will I get nickel and dimed? I wanted to just do a new VM install and move my database over to fix this issue but support said that costs extra. Any suggestions?

Sorry, can't help, hopefully James will see this and help you out.

Bump.

@ffac,

Your solution is to indeed stand up a new virtual machine with SQL Server 2016 64-bit. The work of standing up the new virtual machine with Windows Server 2019 is your responsibility. AC will move your database over for you and take care of the rest for a fee of about $500. Pointing your workstations to the new AC server is also your responsibility as well as coordinating with any interfaces (LabCorp, etc.) for them to move their stuff over to the new server.

In short, this will cost you about a day's downtime and some money. If you are comfortable with all the things that are your responsibility, then paying AC is about all you have to do as most of the interface guys move their stuff for free. If you are not comfortable working with AC or standing up your own VM, pointing workstations, etc. then you can reach out to me to work with AC to turnkey it all for you. My rate is $95/hour.

Note that being comfortable handling such a migration yourself means also having the skill to solve any unforeseen technical issues that crop up as well. Handling the migration yourself with the idea that should something go wrong you can just email me or post on the forum and we will all drop what we are doing to save your hide then and there is not feasible. Such upgrades/migrations need to be well planned events rather than "I'll jump from the plane and ask for a parachute later if my idea doesn't work."

NOTE: I do not support peer-to-peer networks. At all. Also, I do not support any version of Windows older than Windows Server 2019 on the server side and Windows 10 on the client side. If you have older stuff, I can help upgrade it all but that will need to be factored into your costs and time.

James

Thanks James, glad to see you back on the board.

Since my SQL server was 32-bit on my AC server, I was not able to update to SQL server 2016 myself. I had to schedule the update to be done by tech support. It took multiple agents nearly 2 hours and it forced me to AC v11.5 from v11.1.4. The update also forced my x-ray SQL server to have to be uninstalled and I had to move it to its own VM. I spent the whole weekend reconfiguring my server that runs all my VMs. I hope v12 doesn't introduce a whole set of new unforeseen problems. This is why I hate updates/upgrades. Ugh. /r

Thanks for the update. Hopefully Tech support took note of the issues for the upcoming V12 change. I will say that going from 11.1.4 to 11.5 has been a significant improvement in both speed and prescribing issues. I still have some lag for prescribing and other small things but overall 11.5 has been more stable and I don;t see the "prescribing gremlins" I used to have.

A little of a hijacking, but I still would like an answer as to why the initial query for the eRx has to bring over all of the inactive meds. I don't know how their table and query works, but I don't need to go into the 20 drugs that are inactive except maybe every 8th to 10th time. I could wait then for AC to bring over the inactive.

JamesNT could comment here.

Yes, we had support try to install the latest version, and it just wasn't going to happen so we stayed with 11.1.4.

There is no reason why the query in AC should bring over active and well as inactive meds other than someone else thought it was a good idea to do so. One possible reason is seeing the med history may affect a doctor's thought process on what to give the patient next. For example, 6-month follow-up and the doctor decides to give the patient a new med, pulls up the chart and sees, "Wait, I tried that one two years ago. Never mind."

I'm completely making that up, but you get the point. Active and Inactive meds can be separated. My process to convert AC databases to PDF does so. You get two meds lists. One for active, one for inactive.

JamesNT