Home Forums Discussions Problems SQL Upgrade

I am the IT for a clinic and I am looking to upgrade the server from SQL 2012 Express (x86) to SQL 2012 x64 standard to fix some speed and reliability issues. Luckily the office is closed for the next four days so I have time to get this done, finally, but other than references I can't really find any instructions for doing this.

I know how to upgrade SQL Express as I have done it before, but I just want to make sure I preserve the data properly.

WARNING: I am assuming you actually know your way around SQL Server. If you are not an experienced SQL Server Database Administrator, like me, then you should try this on a test server first until you are confident you know what you're doing or you should get a knowledgeable consultant to help you.

Step 1 - Captain Obviously, is to back up your databases. You can use SQL Server backup to do this.

Note: What you are going to do is irreversible. You cannot downgrade back to Express from Standard. Therefore, if this is a virtual machine, now would be a good time to take a check point. If this isn't a virtual machine, have your bare metal restore ready to go. I doubt seriously anything will go wrong as I've never had any bad experiences doing this, but better safe than sorry.

You will need the SQL Server Standard Edition DVD that represents the exact version of SQL Express that you have. While you can move up to SQL Server 2014 or 2016 Standard, Amazing Charts may not support it. You should also try to match up service pack levels. So if you have SQL Server 2012 Express Service Pack 3, you should install SQL Server 2012 Standard with Service Pack 3.

Once the setup program starts, go to the Maintenance section and click on Edition Upgrade. Follow the wizard to complete the upgrade.



Once done, test to make sure AC still works. After that, install all available patches on your SQL Server.

Good luck. You should be done in about half an hour or so.

JamesNT

For further reading:

https://blogs.msdn.microsoft.com/petersad/2011/01/24/how-to-perform-an-sql-server-edition-upgrade/

https://msdn.microsoft.com/en-us/library/ms143393.aspx?f=255&MSPPError=-2147217396

JamesNT

Any advice for moving from x86 to x64? I know it's not an upgrade path, and I'm fine with installing sql 2012 x64 alongside or in a vm but not sure if all I'd have to do after is use the utility to detach and move the db?

Also thank you for the instructions. They don't really tell me anything I didn't already know, but it's always nice to confirm.

Edition upgrade from x86 to x64 is not supported by Microsoft, nor is running x32 beside x64 on the same machine. The only way you could pull off AC on x64 SQL Server would be to install SQL Server Standard x64 on a new VM then move the AC database to that instance of SQL Server via detach/reattach. You would have to properly name the instance of SQL Server and do your level best to incorporate all the settings into SQL Server manually that AC sets up automatically (security, etc.) and then get AC to recognize that instance of SQL Server by manually editing the XML file and possibly a few more things (which I don't remember off the top of my head). You would also need to burn some incense, pray to your favorite superior deity(s), and possibly sacrifice some small animals in hopes that AC doesn't go as far as to check SQL Server details such as x32 or x64 when it starts up (some apps do) and then refuse to run if it doesn't like what it sees.

While I would not say such an undertaking would be impossible as long as AC doesn't check SQL Server particulars that closely (I'm confident I could pull it off), I would say your chances of being in the good graces of AC tech-support would be == 0 once you are finished. Meaning you and you alone would be solely responsible for all issues with AC from here on out and support would always fall back to your setup as an excuse for why you are having any problem you have and how they can't help you.

So unless you really enjoy living on the wild side or have a skillset equal or exceeding mine, I would recommend following the beaten path of SQL Express x86 to SQL Standard x86.

One day, now that you have my curiosity up, I might play with getting AC to run on x64 SQL Server assuming no one else has ever done it. If I do, I'll publish something.

JamesNT

Wait, what are the speed and reliability issues, what version of AC how big is the practice and how many charts? All of these may be issues that may effect reliability and the real question is: Do you need x64?

One version of what James has put above would be to put it on another machine (VM) and install AC which will install x64 SQL light if it is a 64 bit machine (I believe, correct me if I'm wrong please). Then do a backup restore. You may need to talk to AC support to get a license number (depending on version of AC) which cannot be done on the weekend.

This should go smoothly IFF you are using the same version AND you have the correct key, if needed (version 9) AND there is not another issue with the database. That's a lot of ANDs and one big IFF.

I just setup Amazing Charts demo (which is version 8.2.2) on Windows Server 2012 R2 and it set up SQL Server 2012 Express x32. So I assume that is what AC comes with.

JamesNT

I will check with AC on Monday.

I did the same, tried 8.3 and it started to install x86 SQL light.

I tried version 9s but needed a password to continue and it being after hours could not proceed.

I think it may be version 9 that installs x64

From the notes from version 9.1

"SQL Express 64-bit is now supported: For new installs - if the user is running a 64 bit version of Windows, SQL Express 2012 x64 will be installed. For upgrades - if the user currently has SQL Express 2012 x32 then the install will keep that version installed. (AC-7943)"

I have not been able to verify this since I have not been able to complete a clean install from scratch on 9.1 without a key over the weekend.

That certainly is good news, nonetheless. There really is no reason to use 32-bit Windows or SQL Server anymore.

JamesNT

Sorry for the late reply.

The error the office is seeing is an unhandled exception, out of memory when trying to print a prescription.

This doesn't happen if we limit the number to 1-2, but several of our patients receive more than that based on the situation. When we hit over 4 it gives this error consistently and does not print.

Originally I thought it was a print driver error as it would crash only on our sharp. As of 9.3.1 it now crashes on all printers.

Not sure what the issue or solution is now.

I'm assuming the clients and server have sufficient memory.

Which came first: 9.3.1 or windows update. The Windows update has destroyed my ability to pc-fax, so it may not be an AC issue. I suspect SQL upgrade is not going to solve your problem. What was the prior version of AC where all worked well?

Having said that, have you touched bases with AC tech support? Perhaps they have a solution.

Are all of your printers networked or are some set up directly USB? And, if USB, do they have the issue.