What to do after Upgrading GP and/or Migrating to a new SQL Server 

Adjusting Dynamic Budgets after a GP upgrade is typically just a 5 minute task, see the steps below.

If a server migration was involved, please send us the name/instance of the new SQL server and we will issue you a replacement license file.


Steps to migrate Dynamic Budgets to an upgraded GP SQL Server

  1.  Backup and Restore the Dynamic Budgets database into the new SQL server
  2.  Delete and recreate the SQL user login “dynbud” from each database (db_datareader for Dynamics & each GP Company, db_owner for DynamicBudgets)
  3. For each Dynamics GP company database run the following statement to enable the dynbud user with security rights to export budget details back to GP:

    Grant Insert, update, delete, select, references on GL00201 to [dynbud]

  4.  Replace the license.licx file with a new license for the new named SQL server
  5.  Launch the Server configuration Utility, run the upgrade process (verify that you are pointed to the new server)  



  7. Login to the application and change the designated server to the new server in the Database Connections drop down menu.


  9. Open System Management \ Manage Servers, update the name of the server, click test, and if successful, click save.


  11. Test by going to Reports \ Monthly Summary Accounts and try to drill down to transaction details for the live month.
  12. End