GP 2013 to GP2016

(0) Share

Report

Posted on by Community Member

I have converted a company to GP2016, they were using Solomon. I now need to convert our existing GP2013 Database to the same server and GP2016. The problem is if I bring over our GP2013 Dynamics DB I blow away my recent conversion. Is it possible to name the Dynamics Db something other than Dynamics. At what point can I do that? There are separate company DB's.

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (0)

Suggested answer

Bill Campbell 12 on at

Like (0)

Report

RE: GP 2013 to GP2016

It sounds like you are trying to combine the two servers? If that is the case the best option would be for you to create a second instance of SQL Server - named for your company - then migrate your company Dynamics and COMP DB's to that instance.

It would allow you / require actually - to have two or more launch files - one to access One instance and the databases there and the other to access the other instance and those company databases.

Does this help?

Let me know. Just remember to post what you do so others will learn.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: GP 2013 to GP2016

Hi Michael,

Starting with GP 2013 & up, you can actually have a named system DB, not requiring anothe SQL instance, so you can run 2 different GP versions off the same SQL instance..

When installing GP 2016 to create the new server, specify a different name for the system DB (instead of DYNAMICS, call it DYN16 for example) .

Then you restore your GP2013 DYNAMICS and Company DB's over the new SQL server and re-run the upgrade process..

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (1)

Report

RE: GP 2013 to GP2016

Hi,

Just to specify a bit, you can use a different system database only on an initial installation, you cannot 'upgrade' to a different system database name.

Leslie

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: GP 2013 to GP2016

Thank you Leslie for that precision, wasn't actually aware of that. Must say that I've not setup an instance of GP yet with a different system DB name

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

RE: GP 2013 to GP2016

Leslie, does that mean then the answer here would be the Second Instance of SQL? Not sure I am clear on the outcome of the answer.

Thanks also Beat, I had not really consider that option.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: GP 2013 to GP2016

Hi All,

I am wondering if I could create a fresh install of GP2016R2 on a server, then afterward port over the 2013R2 version of our production company. Is that possible using GP Utilities? Basically we are wanting a clean server/install of GP as we don't want to install some of the modules we no longer use in 2013.

Thanks!

Bill

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

RE: GP 2013 to GP2016

As long as your GP 2013 is 12.00.1826 it will work. You will need to run the capture logins scripts and do an install of GP 2016 R2 and run GP Utilities but it will work. Be careful with removing modules. You do not want to leave old versions of tables behind. It is best to uninstall them first before you copy.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: GP 2013 to GP2016

Hi Richard,

Thanks - we are on 12.00.2031 - I believe that's the 2016 Year-End version installed. Will it work with that, or, "only" work on 1826 ?

Bill

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

RE: GP 2013 to GP2016

I have done that particular release but usually as long as you are beyond the release stated you are good. 2031 is later that 1826.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: GP 2013 to GP2016

Thanks Richard. I'll give it a whirl!

Was this reply helpful? Yes No