Performing repository database upgrade
Upgrading a repository database, which needs to be performed only once, adds necessary referencing information to the database to allow for name change propagation to function.If you update TestArchitect Client to version 7.1 or newer from a version older than 7.1, TestArchitect will automatically detect, at first run after the install, whether or not a repository database upgrade is required to enable name change propagation functions. If TestArchitect asks you to upgrade the repository database and you want to upgrade the database, be sure the database upgrade prerequisites mentioned below are met.
Ensure the following requirements are met before upgrading a database.
- The repository database you want to upgrade is a legacy database created prior to TestArchitect version 7.1.
- The repository in which you want to perform the upgrade is not in use.
- All database operations (such as modifying, synchronizing, backing-up, and so on) are stopped.
- All subscribed projects used in the database are available before performing the upgrade.
- You have the built-in user account administrator login privileges for the database you want to upgrade.
After TestArchitect has been installed, open the Repository Server Control Panel.
A dialog box appears to inform you that all databases will be upgraded. This dialog box only appears one time after TestArchitect has been installed.
In the dialog box, you have the following options:
Click OK, if you want all databases to be upgraded automatically.
Click Cancel, if you do not want the upgrading process to take place immediately.
Note:If you click Cancel, proceed to step 3 to manually run the upgrade process for specific repositories.
From TestArchitect Client, log in to the repository that you want to upgrade using the built-in user account, administrator.
In the TestArchitect explorer tree, right-click on the repository and select Upgrade Database on the context menu.
Note:The Upgrade Database option will no longer appear in the context menu once the repository’s database has been upgraded.Confirm that you want to upgrade the database.
Caution:There is no way for TestArchitect to undo the changes made to the database after it has been upgraded.
Optional: TestArchitect may present additional Specify Interface dialog boxes for you to map ambiguous entities, depending on whether or not the database has any such ambiguities which need to be resolved.
Depending on the size of the database, it may take some time to complete the upgrade. An Upgrade Database Tool dialog box appears showing the status of the upgrade and the upgrade results for each project in the database. Successfully upgraded projects are marked with check icons . Projects that fail to upgrade are marked with ‘X’ icons. Click View upgrade log next to a project’s name to view the upgrade log for that project.