The Upgrade Process

The upgrade process will be undertaken by System Administrators responsible for the project at all locations. When upgrading multiple projects, many System Administrators will need to co-ordinate. The upgrade process will upgrade one project at a time. Customers will need to give careful consideration to the order of upgrade for the various projects.

The projects will need to be locked for the duration of the upgrade, with all Users out of the system.

The upgrade process will be:-

1. Ensure all users have exited from project

2. Lock project at all locations (upgrade will check for this (see below)

3. Disable Automatic update events if required. (Recommended but not essential)

4. Expunge all users in the system at the local location

5. Flush data from Working extracts – these will not be considered; in Global projects they should be deleted

6. Check project using DICE (Integrity Checker)

7. [If DICE reveals issues, address them, then re-run DICE]

8. Administrator may want to unlock project while DICE issues are being addressed, but will need to exclude all users and Lock project again before final DICE check

9. [After clean DICE check]

10. Back-up project at all locations

11. Temporarily relocate all non-Foreign DBs to their master’s Primary location

12. Check for No Transient Databases

13. Upgrade the project at each location

14. Optionally Merge Sessions

15. Optionally Reconfigure for Unicode

16. DICE check project

17. Relocate extracts back to their original locations

18. Perform non-framework upgrades if applicable

19. Unlock the project