web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Has anyone had experie...
Microsoft Dynamics GP (Archived)

Has anyone had experience or solution to transfer GP data from SQL2017 to a previous version of SQL?

(0) ShareShare
ReportReport
Posted on by Community Member

GP2013 data was upgraded to SQL 2017 before GP was upgraded to a compatible version.  We need to upgrade GP2013 to GP2016 but are finding that GP Utilities will not run on SQL 2017.  Any suggestions or utilities to work around this issue?

*This post is locked for comments

I have the same question (0)
  • sandipdjadhav Profile Picture
    sandipdjadhav 18,319 on at

    Hello Quinetta,

    I have just upgraded GP2015 to GP2018 on SQL Server 2017. All went well including MR.

    Thanks much

    Sandip

  • Community Member Profile Picture
    Community Member on at

    Thanks for the response but we are on GP2013 and there is no path directly to GP2018.

  • Lucas Miller Profile Picture
    Lucas Miller Microsoft Employee on at

    Quinetta,

    Unfortunately your environment has been put into a state where you won't be able to upgrade at it currently stands.  When other customer's have run into this situation we've performed a SQL "downgrade" consulting service to move them to a SQL version that is compatible with their upgrade path.  We've seen customers request us to include the GP upgrade as part of the service as well as just have the databases returned in the previous SQL version for them to upgrade themselves.

    I'm sure there are other ways to downgrade a SQL database, but nothing that the Dynamics GP team would be able to assist with.

    If you're interested in more information on this service you could open a non-chargeable support case and we could gather the information needed to get you a quote.  Your GP partner would need to involved in this process.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,852 Moderator on at

    Being an old timer I would suggest doing a bulk-copy out and bulk-copy in. I know there are other ways but that  is how I know to do it.

  • sandipdjadhav Profile Picture
    sandipdjadhav 18,319 on at

    Hello Quinetta,

    What is your current SQL Server with GP2013? You can upgrade GP2013 to GP2015 and then move to GP2018 on SQL 2017.

    Thanks much

    Sandip

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    To answer Sandip, it is Dynamics GP 2013 R2 on SQL Server 2017, the issue is that they cannot directly upgrade from GP 2013 to GP 2018 and neither GP 2015/GP2016 is compatible with SQL 2017, hence the issue being seen.

    Thanks

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,852 Moderator on at

    In addition to doing a bulk copy out/in, I would suggest submitting this question in a SQL forum. This is more a SQL issue not a GP question.

  • Community Member Profile Picture
    Community Member on at

    How long have you had the upgrade ?  If you haven't change data in GP, I suggest going to a 2013 restore and upgrade the SQL & GP to a compatible version before going to 2017

    www.mssqltips.com/.../how-to-migrate-a-sql-server-database-to-a-lower-version -  It looks pretty hard and according to the article 'SQL Server does not allow you to restore or attach a database from a higher version of SQL Server to a lower version  of SQL Server'   similar to how you can't downgrade IOS on your iphone because apple doesn't let you (if you had one)

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    Mike,

    You're correct in that you can't take a database from, in this case SQL 2017 and restore it onto SQL 2014 or any older version of SQL, because once you restore a database onto SQL 2017, SQL automatically upgrades it.

    The link you referenced is pretty much what I've mentioned with scripting the database out, so you can then use the script to re-create the database using this script, on the older version of SQL, then you would need to DTS the information from the newer version of SQL databases to the older version.

    Another option that could potentially be used would be to use GP Utilities to create the shell databases on the older version of SQL, then DTS information over from the newer version of SQL, as this would at least give you all the GP objects, though it wouldn't include any third-parties by default, whereas the database script would.

    I'm sure there are probably other methods as well out there.....

    It's not an easy process which is why we only provide it through a consulting service in Dynamics GP support.

    Thanks,

    Derek

  • Community Member Profile Picture
    Community Member on at

    It seems like if he can't run gp util on 2017, GP isn't upgraded.   If it was not a in-place SQL upgrade, boot up the old server.    If it was a in-place sql upgrade, then its tougher.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Anthony Beatty Profile Picture

Anthony Beatty 2

#2
Shravan Attelli Profile Picture

Shravan Attelli 1

#2
CP04-islander Profile Picture

CP04-islander 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans