About Team Server and Repository Upgrade
Go Up to Install or Upgrade Team Server and Repository
Prerequisites
- 64-bit OS.
- Download the latest Team Server installer
- Highly recommended that you back up the database
- Database server where the current Repository database resides
- Database user who owns the Repository objects
- Database user currently must have db_owner (SQL Server) and DBA role (ORACLE)
- Repository Admin password
- ER/Studio Data Architect version that corresponds to the version you to which you want to upgrade must be installed on a separate client machine
Preparing the Upgrade
Repository User Preparations
- Ensure you have backed up all your .dm1 files.
- Check in all your diagrams and objects. If you try to check in a file from the previous version with the same name as a current file, the current file will become corrupted.
- Rename all local copies of Repository diagrams in the active file directory as follows:
- Choose Repository > Options. and make note of the Active File Directory.
- Switch to the Windows Explorer and rename all the diagrams in the Active File Directory in order to protect them of being overwritten. Example: Backup_DiagramName.dm1.
Repository Administrator Preparations
Ensure no one is logged into the Repository, and then back up the current Repository database.
Upgrade scenarios
First of all, prepare the upgrade for any scenario.
Upgrades from Team Server 16.X which includes Repository 7.0.1
- DO NOT UNINSTALL the previous version of Team Server. The new version will back up the data from the previous version and restore it as part of the new Team Server/Repository installation procedure. This procedure allows published diagrams and workspaces to remain published after upgrade
- Install the new version of Team Server.
Upgrades from Repository 7.0.X (Standalone)
- Uninstall Repository 7.0.X.
- Install the new version of Team Server.
- On the repository setup page, select Specify location for Team Server database, this will expand the information fields.
Upgrade Configuration
If you are upgrading from Team Server 16.x or later, you already have one unique combined database, so you can directly follow the steps on the repository setup.
- Check the repository setup and introduce repository database information.
- Select Specify location for Team Server database, this will expand the information fields to include Team Server database information.
- Fill the fields with the Team Server database information with the same structure than you have introduced previously for repository database.
- If your Portal installation was using a separate Solution database, select Specify the location of Solution database.
- Specify Portal Solution database details so the tables can also be copied to the Repository database.
Note for Oracle: Once the upgrade is done, the alias in the tnsnames file must be updated to point the new database server in case you had Team Server and Repository old databases in different machines.
Important Notes
- Always back up databases before upgrading.
- Upgrading diagrams can be time consuming and memory intensive. The number and size of the diagrams managed in the upgrade dictates how long the upgrade process takes.
- Regardless of the process that you must follow to back up your licenses, which depends on the previous version that you are upgrading from and other factors, after you restore your licenses in your new installation, you must log in as a super user and use the Manage Users page to assign different types of available licenses to your users.