Migrate to new SQL server

(0) Share

Report

Posted on by Community Member

Hi,

Due to the end of support for Windows Server 2003, we need to migrate to a new SQL server. We are running GP 10.0, with Encore's Recurring Contract Billing.

I have started our IT Dept. with KB 878449, but was wondering if this a fairly simple process or does it require assistance through a MS support incident/contact our Partner? Also, would it be recommended to upgrade to GP2010 or 2013 at the same time or can that wait till we migrate?

Any assistance is appreciated.

Michael

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Bill Campbell 12 on at

Like (0)

Report

What version of SQL do you think you will update to? What server Os will you land on?

As to update of GP at the same time - I like to be safe and do one update at a time. I am not always comfortable with a 'double' update as it can at sometimes lead to finger pointing if something does not work after the two updates are completed.

As to the question about involving the MS Partner. That is a matter of comfort that you have with performing both updates, all service packs and configuration of various pieces of software during the process. We find that if a partner was involved from the start, there is some level of consistant knowledge of the environment. The partner knows what has to happen with GP to move over the various update blocks, has access to tools and serveices that you might not.

In the end it is your call, you have to decide, but we have over the past 20 plus years never recommended to a client to start, complete or consider an update of this nature without consulting with us.

If you have a problem with your current partner, you can reach out and see who else might be in your area - but - we would strongly recommend engaging with A MS Partner for this project.

Hope this helps get you started. If you want to reach out, see contact details below.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I agree with Bill. Adding to his answer (it might sound obvious... but i went through this so i have to warn you) I would recommend doing the server upgrade first. It could take a very long time to run through the utilities on the older server, especially if you're not on GP 10 SP5 (in which case you'd have to upgrade to SP5, then upgrade to 2013).

I went through this process a couple of years ago. My client was on WS 2000, the server was a dinosaur, and I had 7ish company databases to upgrade. I made the mistake of upgrading to GP 10 SP 5 on the old server before moving the databases to their new server... huge mistake. The GP 10 utilities took ~4 hours to run. Still embarrassed about that one.

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

Like (0)

Report

Michael, you are correct - that is how it should be done.

Update the server first - move the databases to the new server - installation of GP10 (what ever version you are currently on) - make sure it is working before moving forward.

Once you have it running on the new server, move to the latest SP5 for GP10 to make the move to the next release of GP2013 smooth.

Take care. If there is anything else let me know.

Was this reply helpful? Yes No
Suggested answer

L Vail 65,271 on at

Like (0)

Report

Hi,

I'd also like to add that you may not be able to install the client to the new server because it is not compatible. So, you won't actually be able to get version 9, for instance, running on SQL 2014 on server 2012. You'll need to skip the 'make sure it works on the new equipment' step and dive into just moving the databases over and upgrading to whatever the appropriate version may be. Transfer the databases first, and then install the GP client. Don't forget to update the compatibility level of the databases. Get your hands on the KB article that walks you through how to do this, and definitely get a partner involved that has done it before. There are a lot of moving parts to this kind of upgrade/migration.

You'll be delighted once you get to the new version and can enjoy all of the enhancements that they've made to the product. It's pretty amazing what it will do now.

Kind regards,

Leslie

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Leslie for your insight.. I'm going from GP2013 to 2016 and I want move to a new server with a fresh new OS and SQL.. I will do it the way you suggest (without installing GP2013 but just copying the db and then install 2016.. Hoping it will work as we have many extra modules (Mekorma, ePaystub for Canadian Payroll, customization everywhere.... and integrations with other systems... etc etc).. But I always prefer a fresh install to an upgrade so your scenario works for me.. Crossing my fingers.. (but will be doing it as a test only first )

Was this reply helpful? Yes No