This topic explains how to run the SQL Server 9.0 scripts that setup and remove the Image (osImage) and Patient (ukctocs) databases which are required by the URA System
Prerequisites: Your PC must have osImageManagerApp installed (v1.0.0.17 or later) and the database engines installed (SQL Server 9.0)
Note: The default installation of osImageManager is configured so that you can run the UAT on a single PC which acts as a database server for the URA Databases as well hosting the client application.
Setting-up the URA databases for UAT
Note: Installation Troubleshooting provides information about resolving any problems that result from running the scripts in following procedure:
Start osImageManagerApp and logon using a SysAdmin name and password for your database engine(s). For example, 'sa' and the password entered when you installed SQLEXPRESS
Open the Database Admin dialog box and run the following scripts
CreateUsersImage - creates Security Logins for URA-Admin, URA-Operator and URA-Guest on the database engine used for the Image database
CreateUsersPatient - creates Security Logins for URA-Admin and URA-Operator on the database engine used for the Patient database. You don't need to run this script if the URA databases are hosted on the same machine, but doing so has no adverse affects.
CreatePatientDb - creates the Patient database on the server defined by the osImageManager configuration file
CreateImageDb - creates the Image database on the server defined by the osImageManager configuration file
CreatePatientTables - creates the tables required for UAT on the Patient database and makes URA-Admin a db_owner
CreateImageTables - creates the tables required for UAT (or Production) on the Image database and makes URA-Admin a db_owner
Close the Database Admin dialog box and Logoff
Open the Database Admin dialog box and run the following scripts
SetupImageDb - creates the stored procedures, users and permission required for the Image database
SetupPatientDb - creates the stored procedures, users and permission required for the Patient database
PopulatePatientDb - creates the records in the Patient database which are required for UAT (see UAT Document - Appendix A)
TestImageDb - checks that the Image database is correctly installed and configured for use by osImageManager. At this stage there are no records in the Image database so you should just see the column names of the Image table in the Results box.
TestPatientDb - checks that the Patient database is correctly installed and configured for use by osImageManager. The records you created during step 5 iii) should appear in the Results box.
Close the Database Admin dialog box and start your User Acceptance Testing
Removing the URA Databases after UAT
Note: Installation Troubleshooting provides information about resolving any problems that result from running the scripts in following procedure:
Start osImageManagerApp and logon using a SysAdmin name and password for your database engine(s)
Open the Database Admin dialog box and run the scripts necessary to remove the items installed during Database Setup.
DropPatientDb - deletes the Patient database
DropImageDb - deletes the Image database
DropUsersImage - deletes Security Logins for URA-Admin, URA-Operator and URA-Guest on the database engine used for the Image database
DropUsersPatient - deletes Security Logins for URA-Admin, URA-Operator (and URA-Guest) on the database engine used for the Patient database. You don't need to run this script if the URA databases are hosted on the same machine, but doing so has no adverse affects.
Note: After Removing the URA Database you should remove osImageManager from your PC.