2,597
Hi Microsoft,
Is there any way to use GP2015 with SQL 2017.
I have a customer using GP2013 and upgraded his SQL to 2017 and his GP2013 Build can only upgrading to GP2015, So i am stuck now.
Any Solution for this issue.
Thank you.
*This post is locked for comments
Hi Hossam,
There might be some hope if you're still stuck in this setup... Read on the blog post from David Musgrave
Good point Beat. I neglected to mention that. It all depends on how much data has been entered. There is no easy solution. Whoever did the SQL upgrade is responsible for this mess. The funds need to come out of their budget to correct this.
If they already entered data in that SQL instance while running on SQL 2017, then it's too late to resort to the old backups.. they are useless at this point.
The only option Microsoft is going to do, is bulk export all your data from GP 2015 in your SQL 2017 instance and re-import them into a lower SQL version (i.e 2014) to be able to perform your upgrade to a new version of GP.
That's the only way to go when you have no current backup from an older SQL version.
When did the SQL upgrade occur? Have they entered data since the upgrade? How much data? They may be running right now but any future GP upgrades will not be possible. My thinking is to create an image back to the day before the SQL upgrade. Put SQL 2014 on this image. Restore all the databases and then they will need to re-enter all transactions. Once that is done you can upgrade to GP 2015 or GP 2016. You could finally move this data to the SQL 2017 image and upgrade to GP 2018. The longer they keep using the current installation the worse this becomes. It just means more transactions will need to be re-entered. There is no easy solution here. This is a mess. If you require assistance with this let me know. We do GP upgrades all the time and have images ready to upgrade any version of GP.
Hi Richard,
Yes there is Full back but there is more than one month data so i can't just use old backup.
what is your idea exactly?
Thank you for your time and waiting your reply.
Do you have backups prior to the upgrade of SQL? If you do the simplest thing to do would be to install a second instance of SQL that matches the previous version of SQL. Follow the steps in KB878449. This will get GP running again. If no backups are available your only choice is to upgrade to GP 2018. The problem here is you are going to need an instance of SQL 2014 running to make the hop to GP 2015 or GP 2016. Hopefully you are running images and can fire up up the images that are configured properly for the version of GP you are using. As Lucas mentioned the version checking that GP Utilities will perform dictates what is required. If possible, I would engage your GP reseller on this project. You have already experienced what happens when those with no GP experience start making changes.
this is SQL upgrade
Hello,
Dynamics GP itself will often work with unsupported/untested versions of SQL Server, but you will definitely be version checked when you try to run Dynamics GP Utilities to perform an upgrade or create a company and you won't be able to proceed.
The SQL compatibility requirements that Richard mentioned are correct.
Since you're on Dynamics GP 2013 you can only upgrade to GP 2015 or GP 2016. Neither of those are compatible with SQL 2017, so you're only option is really to downgrade SQL to a compatible version. That is a tricky process since the databases would have been upgraded as soon as you restored them to SQL 2017 and that means you cannot restore backups to an older version of SQL.
We have done SQL downgrades as a billable advisory services in the past so if you're interested you can open a support case to begin the process of getting a quote. You could also check the Microsoft Pinpoint site to see if there are other partners who provide that service.
Lucas Miller
Microsoft Dynamics
You only have two options.
Option 1) Upgrade GP to 2018
Option 2) Downgrade SQL to 2014
Can you install SQL 2014 as a second SQL instance? When they installed SQL 2017 did they perform an actual upgrade or did they install SQL 2017 as a separate instance? I have seen this plenty of times before. IT staffs just start upgrading that which they know and the heck with everything else.
Hi Richard,
I am on this situation now, The Customer IT upgraded to SQL 2017 without checking with me.
so what is the solution now.
as i mentioned my current GP Build Number not allow me to upgrade to GP2016 so i forced to upgrade to GP2015, and GP2015 not supported by SQL 2017.
By the was GP2015 is working with SQL 2016, Microsoft must upgrade the system requirements document for all versions.
Wish you can give me a solution.
#1
André Arnaud de Cal...
291,602
Super User 2024 Season 2
#2
Martin Dráb
230,340
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
