GP 2010 Moving to new sql server

(0) Share

Report

Posted on by Community Member

We are kicking up a process to move our existing GP environment to a new sql server. Since we currently have just a client server setup with no master client I am wondering how I point the GP clients to a new SQL instance. Any assistance would be greatly appreciated.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (2)

Suggested answer

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

Like (1)

Report

Hi Jennifer,

What is your current SQL server version ? and your exact GP 2010 version ?

Check the following community thread that contains all the links to the valuable information and KB's you need for this process to be a successful project.

community.dynamics.com/.../microsoft-dynamics-gp-2013-upgrade-paths-_2d00_-gp_2c00_-windows_2c00_-sql-server

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (0)

Report

Beat is right in pointing you to the Blog it does contain a great deal of information on the various process you 'could follow'

The good news is that when you finally get the server configured, and you have GP2010 installed on a workstation, following the steps to configure the ODBC (32bit) will 'point the client the new sql instance'

Note that it is via the ODBC connection and not much else that GP communicates to the SQL Server. If you miss that step, you will not get GP2010 to operate.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Currently we are running GP2010 SP4 Version 11.00.2320 on SQL Server 2008 R2. We are looking to move the databases to SQL 2012 R2.

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (0)

Report

So, do you consider this a new Server - physically - or are you updating the SQL2008 to SQL2012 on the same physical machine?

Reason for the question is that in one case it is an update of the SQL Server and not much else changes. In the other, you are starting a new machine and installing everything new (SQL2012) and then MOVING the existing Dynamics installation onto the new machine.

Both will and do work. You just need to define which one you are likely to be doing and then the answers are easier to formulate for you.

Was this reply helpful? Yes No
Verified answer

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

Like (1)

Report

Jennifer,

You should not encounter any major issues with upgrading from SQL 2008R2 to 2012...

However, keep in mind :

1. the new server will likely have a different machine name than your old server.. this will mean that your client ODBC connection will have to point to that new server in order for your GP to work with the new SQL instance

2. by changing the server name, your password encryption will not match anymore the one from the old server (encryption is based on the server name in the ODBC string), so it's a good practice to use an ALIAS in your DNS which can then switch easily without having to reconfigure all your ODBC clients (I use DYNAMICSGP as alias for my GP production system). The only user that will be able to login will be the 'sa' user, as that user pwd does not base the encryption on the server name.

3. Doing a backup after the SQL restore on the new server is a good idea, as your DB's will all be upgraded on the SQL server side (not GP), to comply with the new version. Check if your DB compatibility flag is set to the latest release (it should be 110).

For the server ALIAS, ask your IT guys to put that under the new server entry in the corporate domain DNS and create your new ODBC right away with the new name.. will save you quite a few headaches for the future migration.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

This is a new physical cluster due to moving our data center to a new location. We are not upgrading the current 2008 server but rather standing up a new cluster.

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

Like (1)

Report

Well done Beat.

That is exactly what I was wanting to know and you beat me to the punch on the reply.

We have had no issues moving the Dynamics databases to new servers as long as we follow the process and steps outlined. The points Beat makes are very important and should be key to making the migration work for you.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you Beat. Do you know if there is a similar procedure for Management Reporter as these databases will be moving with GP.

Was this reply helpful? Yes No
Verified answer

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

Like (0)

Report

Hi Jennifer,

The ManagementReporter12 database (as it is named by default I believe) can be restored on the new server the same way as your GP DB's.. all you have to make sure is that the proper security accounts are setup on the SQL side (i.e. MR runs usually under a domain service account).

You don't need to worry about the MR DataMart database, as this one can be easily rebuilt on the new server when installing MR 2012. If you install a different CU on the new server, MR will ask to do an upgrade of the database first before you can use MR in the configuration console again.

Hope this helps..

Was this reply helpful? Yes No