I have a client that has over 30 companies in GP2010. We are starting plan the upgrade to GP 2013. I have a question about doing this as a staged project, upgrading a set of companies every couple weeks. We are looking into this due to the complexity of multiple integrated solutions with each set of companies.
Does anyone have insights into this idea?
Thanks,
Scott
*This post is locked for comments
Leslie and Richard are correct. The only thing I have to offer is that remember you can upgrade companies on multiple instances at the same time as long as your SQL server has the resources. Often times people will do 5 companies on each machine that way you get 10 companies upgraded in the same amount of time it would take if you were only using one install.
Hi Scott,
Richard fired off some great questions. I've have many clients want to do this because they figured they could just keep running the 'old' version on some companies, and the new version on the companies as they were upgraded.
Unfortunately, it isn't that easy. Once you install the upgrade, the first thing you have to do is upgrade the 'system' database. That would be your DYNAMICS database. Once this database is updated, you can no longer access the other companies using version 2010. It doesn't matter that those company databases are still at GP 2010, you cannot access them. If you're switching equipment, or have two instances of SQL AND GP installed, then you have a different story. If you weren't planning on having two different installations, then you cannot l'stage' the upgrade and still access all of the companies.
That said, what you CAN do is update the companies in a certain order such that the most critical companies come on-line first. You can update the other companies later, but nobody will be able to work in them until they are upgraded. With 30 companies, you probably don't need them back on-line on day one. I have done this sort of staging many times. The only trouble I've ever had is when the client was operating on a build that needed to be updated before they could upgrade to the next version. I had to bring all of the companies up to the new build first. But, after that, the staging worked just fine.
I'll mark this 'suggested' only because I don't know if the change has been made yet on how the forum was being displayed.
Kind regards,
Leslie
That would depend on the segregation of the companies. Do all of the users need access to all of the companies all of the time during the upgrade process? It would be preferred not to have two versions of GP on each workstation. Is this going to be an in place upgrade on the server or will GP 2013 R2 reside on another server? Will the version of SQL be remaining the same? How about the OS of the workstations? GP 2013 R2 requires W7 as a minimum. As you can see there are many questions. Do you have any specific questions? It can be done but you need to be careful of the order in which things are done.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (