Home Forums Discussions General Discussion SQL upgrade

Hi,

Mark@AC or someone can help on this: the minimum hard driver space for the SQL upgrade on the server computer is 1TB. My computer HD is only 1TB, and there is 660GB free space now. Should I go ahead with the upgrade or replace it with a new computer?

Thank you in advance!

Believe you are referring to the minimum recommended requirements of entire hard drive space for total install of AC, assuming you are already running AC on your server believe you need a minimum of 6 GB available free space to do the SQL 2016 upgrade see here MS info

You are not going to need 1TB of space for this upgrade. The 1tb we mention in the instructions is for Amazing Charts as a whole, and that is mainly for imported items. 660GB is plenty of space to do the upgrade.

Thank you, Mark@AC and Koby, that's great!

Finally did the SQL 2016 upgrade on my main office server running Windows Server Essentials 2012 R2 and it went well other than having to reboot the clients afterwards so they would connect. Guess I'm good till Oct 2023 when WSE 2012 goes 'unsupported' by MS. Gee what will happen first; retire or upgrade to WSE 2016 ????

I have upgraded to MS SQL server 2016(ver 13), rebooted server - but yellow warning regarding HIPAA compliance still there. Is it OK? Have you message gone after MS SQL 2016 has been installed?
Thank You I appreciate your answer - not sure if I need to contact AC support?

My AC installed on SSL drive .5Tb(500 Gbyteds) and I didnt have any problems (My database is huge ~ 45Gbytes)

Once I did the 2016 SQL upgrade I deleted the message in my inbox and it hasn't reappeared, don't think it is a 'smart' message ie not a checker of current configuration. Just like the darn message about ePrescribing warning on AC login screen about versions <11.

The message will not disappear. It is just a general message in a box, kind of like a banner add on a webpage. It is not dynamic. It will stay there till we turn it off universally or change it.

Hi MArk@AC,

I did the upgrade, and everything appears to be fine. But, for the backup, I always receive the following email: "Backup plan Amazing Charts SQL Backup COMPLETED See the details below:

ERROR: One or more databases are not found" with the following note: "Note: You have one or more files on your online storage scheduled to be permanently deleted in 0 day(s). Open Amazing Backup console to view these files."

Does this mean that all the backup files will be deleted at the same day it was created?

What should I do?

Thank you!

never mind, I received a call back from AC support - David, he is fixing the problem.

Thank you,

SQL upgrade went haywire on our system. As far as I can tell it deleted the existing database and now I can't reinstall or remove amazing charts to restore a backup. Anybody have a similar issue so I can get back to the original database?

OUCH, let us now what happens!

I received the same message and sent question to Support via email.
Also I ran cloud backup manually and it was successfull - so not clear if this is real issue or not.
Local back doesnt have any issues

Thank You!

I just received email from tech support: They have to fix Backup setting on their side after upgrade : simply send email to techsupport@amazingcharts.com and they will handle the rest

Got an email today from AC about the upgrade, which is good. (A regular email, not in the program).

However... it says this if you do the upgrade yourself: " Self-Serve – Click here to access the step-by-step guide for completing the upgrade. Please ensure you have an IT professional on your end if you choose to use this option.

I thought we were told this was an easy process that did not require IT support.
Does this represent a change?

(Asking Marc, Chris Conrad, and any other reps of AC who might be here).

My setup generated a warning about domain controller. I tried to contact Harris, but agents are not available. What a disaster!

SO it didn't wipe out the database????
Did you ave to restore AC????

Please keep us posted how this resolves!

If you're at all technically inclined you can do this update by yourself without IT. The recently published procedure is simpler and much less risky than the previous one. Significantly!!!.

You just need to be careful and use the new one..not the old prior one..some people downloaded the older one locally when the links were available and are not reading the instructions and are having problems. It's not that the old one was bad...it just did many more things that creates the opportunity for problems if the planets aren't all aligned and you can imagine what we have out there to deal with.

Instructions say don't use upgrade if the AC "main" computer is a domain controller. So is a server with DC and AC on same machine ok or not to upgrade? Alternate procedure? Or do we have to separate out the AC on a separate VM/server and then upgrade?

If you're using a domain controller you'll need to call support...they've run into a couple of these in the past few days and there are a few other steps that will need to be done...

Please tell me again what happens if we DON'T upgrade?
Sky falls?
System slows down?
I'm going to retire in 5 months, and I don't want to have to deal with a broken system at this particular time.

Or a devious employee with access to a database of all those practices who have not done the upgrade reports it to Unc Sam to collect his part of the fine money.

It's not paranoia if it's true, LOL!

5 MONTHS!!!!!! CONGRATULATIONS!!!!!!!

Just get AC Tech to help, if your luck is like mine, something will happen and the fine will be assessed on the last day before you retire!

Here is the low down with a quick google search: "medical providers (or any health or human service provider) are held accountable for both the privacy and safety aspects of the law. Any violation of the HIPAA Administrative Simplification rules will result in an investigation and possible civil money penalties, jail time, etc.–depending on the breach of data."

Tier 1: A violation that the covered entity was unaware of and could not have realistically avoided, had a reasonable amount of care had been taken to abide by HIPAA Rules
Tier 2: A violation that the covered entity should have been aware of but could not have avoided even with a reasonable amount of care. (but falling short of willful neglect of HIPAA Rules)
Tier 3: A violation suffered as a direct result of “willful neglect” of HIPAA Rules, in cases where an attempt has been made to correct the violation
Tier 4: A violation of HIPAA Rules constituting willful neglect, where no attempt has been made to correct the violation

Tier 1: Minimum fine of $100 per violation up to $50,000
Tier 2: Minimum fine of $1,000 per violation up to $50,000
Tier 3: Minimum fine of $10,000 per violation up to $50,000
Tier 4: Minimum fine of $50,000 per violation

The above fines for HIPAA violations are those stipulated by the HITECH Act. It should be noted that these are adjusted annually to take inflation into account.

After waiting many weeks to do the SQL server 2016 upgrade, I tried to do it this weekend, but unsuccessful. I am using the latest install guide released a couple days ago. During setup, the installer is supposed to let you select the instance of SQL server to upgrade, but this option is not listed and goes straight to install. It only installs SQL Browser and SQL Writer. The "Database Engine Services" and "SQL Client Connectivity SDK" are not installed; therefore, I only get 2 green checkmark vs 4 listed in the install guide. I then had to roll back my VM to before attempting to get my environment back up and running.

Hi Chris,

According to the Farmer's Almanac, the planets should next align in 2024.

Thank you Chris!
It's important to know the options.
I think I will choose Tier 1.
Tier 4 doesn't seem real appealing.

My only hope is that the HIPAA wheels move slowly enough that I can coast through the finish line before the Behemoth can catch up.

It's just like Windows XP going EOL. A lot of people took their time. Microsoft just stops making updates for it. Doesn't necessarily mean it's going to explode on the day it goes EOL.

My upgrades have been going smoothly so far. It's a very similar process when you upgrade SQL Express to Standard. For the people upgrading from SQL 2012 Standard, you'll need to make your own slipstreamed SQL 2016 Standard installer with Service Pack 3. Then go for the upgrade. There's no SQL 2016 Standard SP3 installer like there is for Express.

Exactly.

Folks, we have been through a series of these "scares" over the past decade...
"Don't participate in the EMR incentive program with the Feds... they will give you the money, then audit you and claw it back".
"HIPAA is coming. Watch out for the HIPAA police... better pay for a consultant or at least a seminar to advise you or it could cost you thousands of dollars".
"Don't do MACRA/PQRS/MIPS or whatever it is called this week ... the government will screw you!"
"ICD-10 is coming. It will transform your practice of medicine! Better take a course... or hire a consultant. How will you know how to code... you will lose millions".
"Windows 7 is sunsetting. You won't be HIPAA compliant anymore! Huge fines are coming!"

Now it is SQL server 2016.
I am tired of the "running around with hair on fire" stuff.

When it is easy to install and when I get to it, I will upgrade. When you start hearing about HIPAA fines to tiny practices because their software is 3 months past EOL, then let me know.

Meanwhile, I have a practice to run.

I will have to disagree regarding SQL Server 2016 Standard not coming with SP3 slipstreamed into the installation.

JamesNT

Regarding upgrading, there are reasons to upgrade. In no particular order:

* To maintain support. Vendors cannot support everything under the sun. It's just not feasible. Time moves on, new stuff comes out, and the old stuff settles into history. It's getting more and more difficult to find support for things such as Windows 7, Windows Vista, And Windows XP. On the server side that would be Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003. I currently support about half a dozen Windows Server 2003 installations between two clients. I have been begging those clients to upgrade for years now. One is finally moving forward. The other shows no sign of doing anything. How much longer do any of you think I can keep Windows Server 2003 going? One day in the not distant future, that client's Server 2003 installation will blow up or not be able to do something and he'll be stuck. And my only answer will be to find a good bankruptcy lawyer in his area. He's already expecting me to find solutions for printing because the brand-new printer he just bought doesn't have 2003/XP drivers so that means using the generic driver which means no color and no front-and-back printing.

* Efficiency. Windows Server 2003 was wonderful back in the day. And I miss, with all my heart, Windows NT 4.0. I still have a copy running in a VMWare virtual machine because I'm nostalgic like that. But there is no way I would support that stuff anymore for a new client. It's horribly inefficient from every angle you can imagine from no support for USB to no way to managing power consumption like what we have today.

While I certainly do empathize and sympathize with being told yet again it's time to upgrade, proper IT scheduling is what will save your bacon and your wallet. The only real issues I see are from the DIY crowd. It may be time to ask for some help. My SQL Server 2012 to 2016 upgrades have gone without a hitch every single time. But then again, I live and breathe SQL Server every day.

JamesNT

I agree with Jon.
What happens if we don't upgrade SQL 2012 to 2016? Does the AC program stop working?

What does it mean that it is HIPAA non-compliant?
It must be some arcane notion about the way to provide copies of records. Our way of sending PDF's by fax or mail hasn't been challenged. Is that going to change?

Allow me to elaborate further.

No, Amazing Charts will not stop working if you don't upgrade right now. However, the following will eventually happen and when I say eventually I mean probably over the next 3 years or so (your mileage may vary):

* You will call AC support because of some error and they will refuse to help until you upgrade your SQL Server.
* You upgrade Amazing Charts and then things break. The reason why is Amazing Charts is utilizing a new feature of SQL Server 2016 that 2012 doesn't have.
* You decide to upgrade your server and you purchase a new copy of Windows Server 2022. But you can't use Windows Server 2022 because SQL Server 2012 is not compatible with it.

So for those of you that want to put off upgrading from SQL Server 2012 to SQL Server 2016 feel free to do so. The HIPAA cops will not come for you. Your network will not stop working. Your building will not catch fire. Your life will not end.

The problem is you'll forget all about this easy upgrade and then one day one of the above things will bite you in the [censored] and you'll just stand there with that look on your face of, "Gee, I guess I forgot that."

If any of you need assistance with your SQL Server upgrade, feel free to reach out. You can PM, email, or call me. Contact information in my profile.

JamesNT

Thanks James -- I am fairy confident that the upgrade would be easy and go smoothly in our little network, and I know that you and Sandeep could help if it didn't.

My situation is a little different -- I have 5 more months committed to keeping the practice open, then I'm done..

I am choosing between two small probablity states -- on the one hand the chance of failure of the upgrade is small, and on the other, the chance of the current setup failing before Dec 31 is small.

@Tomastoria

For yourself, or anyone else retiring in the next 12 months, I wouldn't care about the upgrade. At all.

JamesNT

But why not if you're willing to help!

Of course My philosophy is we pay for support, try it, if it doesn't work get them on the line and let them fix it, AC is their baby, Tom just wants to take care of his people.

@Chris,

Good to hear from you again. Hope you are well.

While I do certainly understand your philosophy, I'm afraid I cannot agree with it. If your SQL Server upgrade goes south for whatever reason, then your practice is down until you can get support on the phone and support fixes the issue. That could be a few hours to a couple of days depending on how backed up AC support is. The problem is made even worse by those out there who have bare-metal installs because that almost totally wipes out the choice of just standing up a new server and moving the database over to recover quickly. And even for those that do virtualize, standing up a new server may still not be much of an option because they have EVERYTHING installed on one virtual server (Amazing Charts, SQL Server, domain controller, gateway server, DHCP, DNS, and so on) so standing up a new server is now an all-day affair rather than 2 hours of work.

Upgrading from SQL Server 2012 to 2016 should be a planned weekend thing, should take no more than two hours, and should be done after fresh backups are taken and a snapshot created in whatever hypervisor the sever is using. But that's assuming your servers are CLEAN, meaning they don't have mixed roles and lots of "toys" from your IT person installed on them and are virtualized. That's the biggest problem I've seen from the offices whose IT I have taken over the past 12 months: tons of completely unnecessary garbage installed on one server or one server expected to just do everything. Not good.

JamesNT

Why wouldn't one put DNS, Active Directory, Domain Controller and DHCP (sometimes) and the programs and databases on separate VMs. And, why can't you do a backup PLUS a check point?