This topic explains how you can update the SQL Server 7.0 production databases used by URA v1.0.0.14 so they can be used by URA v1.0.0.17
Prerequisites: Your PC must have osImageManagerApp (v1.0.0.17) installed and be able to access the server(s) that host the production databases.
CAUTION: Before updating your production Image and Patient (ukctocs) databases you should install URA in your System Test Environment and complete the UAT to assure yourself that the new version is functioning correctly. You should also perform a complete backup of your production databases before running the update script in case there are problems and the rollback script fails.
Running the Update Script for SQL Server 7.0
Note: Installation Troubleshooting provides information about resolving any problems that result from running the scripts in following procedure:
Remove osImageManager v1.0.0.14 from the PCs belonging to other users of the URA System taking care to backup the necessary files
Start osImageManagerApp (v1.0.0.17) on your PC and logon using a SysAdmin name and password for your database engine(s)
Open the Database Admin dialog box
UpdateImageDb - updates the Image database; see Release Notes for details of changes
UpdatePatientDb - updates the Patient database; see Release Notes for details of changes
Close the Database Admin dialog box and Logoff
Check the URA System to confirm it is operating correctly
Install osImageManager v1.0.0.17 on the PCs belonging to other users and edit their osImageManagerApp configuration files so that the production environment settings are retained
Allow other users to access the URA production system and draw their attention to the new features and changes in osImageManager v1.0.0.17
Running the Rollback Script for SQL Server 7.0
Note: Installation Troubleshooting provides information about resolving any problems that result from running the scripts in following procedure:
Remove osImageManager v1.0.0.17 from the PCs belonging to other users of the URA System
Start osImageManagerApp (v1.0.0.17) on your PC and logon using a SysAdmin name and password for your database engine(s)
Open the Database Admin dialog box
RollbackImageDb - restores the original stored procedures and security logins on the Image database
RollbackPatientDb - restores the original stored procedures and security logins on the Patient database
Close the Database Admin dialog box and Logoff
Remove osImageManager v1.0.0.17 from your PC and install osImageManager v1.0.0.14. Restore the Configuration file as well as any other files you have backed-up.
Check the URA System to confirm it is operating correctly
Install osImageManager v1.0.0.14 on the PCs belonging to other users of the URA System
Allow other users to access the URA production system and inform them that osImageManager has been rolled-back to v1.0.0.14