GP and Database Connection Details

(0) Share

Report

Posted on by Community Member

Hi,

We are presently running Windows Dynamics GP 2013 on Windows 2008 Standard Edition on 2 Physical Machines (Dell). One machine is running Windows GP software and other one is running Windows Sql Server 2008. Now we need to do Physical2Virtual conversion for these 2 images and migrate Windows GP to VMs on Windows 2012 Hyper-V. Due to this P2V the IPAddress range of Windows GP and Sql Server will get changed. Before doing this exercise we want to make check how the connectivity b/w GP and Sql Server is done aka either through hostname/dnsname or through IPAddress.

Can somebody point us where to check in Windows GP the database connectivity information.

Also, any other thing we need to take care in Windows GP or Sql Server before or after the migration like Stopping the Sql Server Service before conversion starts.

Thanks & Regards

Ankush Grover

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

MattPaulen 6,912 on at

Like (0)

Report

If I understand your question correctly, it's a 32-bit ODBC connection that GP uses to connect to the SQL server. You should be able to see the current connection by opening up the data sources and clicking on the System DSN tab.

Was this reply helpful? Yes No
Verified answer

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

Like (0)

Report

Hi Ankush,

This mostly will help you in your setup :

support.microsoft.com/.../918983

Also, the reason why I use 'Aliases' in the DNS to point to the real name of the Dynamics GP SQL server is exactly for this reason... when moving your GP database server to a different system, if your ODBC connection server name changes, you'll have to reset all the GP user's password.. whereas with an Alias, the Server name remains the same.

Was this reply helpful? Yes No
TSMurphy 372 on at

Like (0)

Report

This is the method that we have used. Build out the VMs from blank slate with different IPs. After GP has been installed and all applicable add-ons, backup DYNAMICS and Prod/Test dbs from original server, restore to VMs. Set db compatibility if SQL versions change. Pick a cutover time and switch IPs to the original production servers. As pointed out, make sure the ODBCs are correct and make adjustments to DNS.

Best to make a few dry runs developing a checklist has proven to be very helpful from past experience.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Timothy

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Matt.

Was this reply helpful? Yes No