You are viewing an old version of this page. View the current version.
Compare with Current View Page History
Version 1 Next »
https://help.myob.com/wiki/x/VoTeAw
How satisfied are you with our online help?*
Just these help pages, not phone support or the product itself
Why did you give this rating?
Anything else you want to tell us about the help?
This page explains the upgrade process for an organisation that uses multiple versions and databases in one Hr.ini file, which is the recommended setup (best practice).
PayGlobal does not allow you to install two builds of the same version on the same machine. For example, you could not install 4.14.0.0 and 4.14.0.1 on the same machine, but you could install 4.13.0.1 and 4.14.0.2 or 4.18.0.0.
This manual assumes that:
- You're already using a PayGlobal database.
- You use multiple versions and databases in one Hr.ini file, which is the recommended setup.
- You have a supervisor user profile and you can run the entire PayGlobal upgrade procedure.
- You're a member of the sysadmin fixed server role, with security permissions to restore an SQL database.
If you use multiple versions and databases with one Hr.ini file, then your file structure will be like the following example.
In the Hr.ini file, each database will have a CompanyPath (path to the company data folder) and a RunVersion (the PayGlobal version that the database is using).
The RunVersion value must have a corresponding [RUNVERSION_value] entry. The [RUNVERSION_value] entry contains the RootPath to the Hr.exe and all other associated files for that version of PayGlobal.
The shortcut on your desktop will point to StartPayGlobal.exe in your primary Exolvo folder. StartPayGlobal.exe opens the PayGlobal splash screen and if Hr.ini contains multiple companies, then it lists them alphabetically.
Creating new test database
Always upgrade your test database before you upgrade your 'live' database so you can check that everything works correctly in the new version, such as your designer reports. However, the test database must reflect the status of the 'live' database so you need to create a new test database for every upgrade. In Back up Databases, you took a backup of your current 'live' database and now you will restore from this backup to create a new test database.
Only members of the sysadmin fixed server role can restore a database.
When you restore from a backup file, the MDF and LDF files are extracted from the backup and copied to the default Data and Log folders in your SQL Server folder.
- Copy the backup file to a folder on the SQL Server machine or a UNC shared folder that the SQL Server account has Read access to.
UNC pathing requires the folder to be a network share. The service account used to run the SQL Server service must have full Modify rights to the shared folder. To check the which service account is in use, you can go to SQL Server Configuration Manager. - Click the Windows Start button.
- Use one of the following options to add the path of the current PayGlobal Hr.exe:
- In Windows Explorer, navigate to the PayGlobal Hr.exe, and then drag-and- drop it into the Open field in the Run box.
- Type the Hr.exe path into the Open field in the Run box.
If the Hr.exe path contains spaces, then you must enclose it in double quotes.
For example:
"C:\PayGlobal\Versions\4_14_0_2\Hr.exe" After you add the Hr.exe path, type a space, and then /initsql. For example:
"C:\PayGlobal\Versions\4_14_0_2\Hr.exe" /initsqlClick OK. The Company Setup form appears.
- Enter the following details:
Field Details Company Name (Blank) Path Type the path to the Test folder in your Companies directory, such as C:\PayGlobal\Companies\Test\ Serial Number (Blank) Client Number (Blank) Database type SQL Server Country Select the relevant country, such as <_Country>. Server name SQL Server machine where the database will be created and stored. Database name Name of the test database, such as Test.
You cannot use a number as the first character in the database name. The database will not be created, and the following message will appear in the audit log: Line 1: Incorrect syntax near [database name].
If you already had a test database, then you would have to use a different name or delete the original test database in Microsoft SQL Server Management Studio.
PayGlobal user Accept the default, which is PGUser_(Database name).
The PayGlobal user must be unique to each database. You are creating a test database so the PayGlobal user will be PGUser_Test.
Restore login Accept the default, which is PGRestorer_(Database Name) because each database on your SQL server needs a unique Restorer login.