web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / SQL Databases
Finance | Project Operations, Human Resources, ...
Answered

SQL Databases

(1) ShareShare
ReportReport
Posted on by Community member 2
Hi i have 2 quick questions
 
We are running GP2018 on SQL 2019 and i have been requested to upgrade, i would prefer to do a complete new install on a new windows box, one question if i create a separate Drive to hold the databases i restore the databases using T SQL Restore and Move who does GP application know where the DBS are? 
 
Also and a much prefered option is to move the DBs to Azure is this possible? 
 
Many thanks 
Categories:
Microsoft Dynamics GP
I have the same question (0)
  • Verified answer
    Joseph Markovich Profile Picture
    Joseph Markovich 3,976 on at
    Hi Ian-
     
    There is a whole set of steps with moving the GP databases to another server. When you move them to another SQL Server, the DB files and log files will be placed wherever you set up in SQL Server to store the DB and log files.
     
    Here's the guide on Microsoft Learn for that:
     
     
    GP knows where the files are from the ODBC connection to the server.
     
    On your Azure question, there is a great article on Microsoft Learn about moving GP to Azure and everything you'll need:
     
     
    I hope this helps.
    Joe
  • Suggested answer
    Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    Let's assume your new and old servers are on the same network. You set up your new server with W2022 Server and SQL 2022. You install GP onto the new server taking note of your current account format. You launch GP Utilities on the new server and go through the usual steps. The missing step is creating your company database. Do not do this. You then take a backup of the databases and copy them to the new server. You perform a forced restore of the DYNAMICS database and then restore your company databases. You will also need to capture your logins by running the script in KB 878449. You finally log into GP on the new server, run the captured login script and proceed to change everyone's GP passwords. A final step in SQL would be to make sure the database owner is set to DYNSA and the SQL compatibility is set to SQL 2022.  On the workstations you go into the 32 bit ODBC administrator and change the name of the server for your DYNAMICS GP 2018 to the name of your new server. The process is similar for an Azure or any other cloud server.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 544 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 250 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans