Upgrade with SQL Server MigrationsIf you are on a legacy version of the app, you will have a few extra steps. We will need to know the new SQL Server Name\Instance too issue you a new physical license.
You will copy the new license into the DynamicBudgets-App folder replacing the prior license file.
You will physically copy the new application files and paste/replace in the DynamicBudgets-App folder. If your staff run Dynamic Budgets from a shared folder, you will have to have all users logout, or you will have to kill any open processes if the user is not responding.
Working with your budget administrator, we will run the server config update utility and point to the new SQL server to rebuild the data adaptors to GP. Next, we will log into the app, goto Manage Servers, and update the SQL Server reference, test the connection, and save.
This is the biggest advantage of the new application, users do not need to log out of the app while we run and upgrade, even if on a centrally installed TS or Citrix server, the App Launcher will download a new datestamp folder for the new build. Active sessions can continue to work while we upgrade.Once the upgrade is complete the budget administrator will ask your staff to log out and log back in, and their clients will download and launch the latest build of the software.