Upgrading the Repository

When an administrator upgrades their PowerDesigner client and then connects to an existing repository for the first time, they will be prompted to upgrade the repository. Until an administrator upgrades the repository, other users who have upgraded their PowerDesigner client will not be able to connect to the repository.

1. If you have installed the PowerDesigner Portal, you must stop the PowerDesigner Portal Service before upgrading the repository.
2. Open PowerDesigner and select Repository > Connect to open the Connect dialog.
   Only the PowerDesigner modules that are installed on your machine will be upgraded in the repository database. For example, if you do not have the Object Oriented Model installed on your machine, that part of the repository database will not be upgraded. For this reason, you should try to perform the upgrade from a machine that has all of the modules used by your organization installed.
3. Select a direct repository definition from the list, enter your password, and click OK.
   Note: Upgrading the repository via the proxy is not supported.
4. You are prompted to update the repository. Click Yes to continue and open the Repository Update Script dialog.

   Depending on the size and complexity of your repository, this dialog may take several minutes to appear.

   Note: If you created your repository database with Microsoft SQL Server or Sybase ASE before PowerDesigner version 15.0, we recommend that you select Rebuild clustered indexes in this dialog to improve performance, particularly for document check out. If you do not select this option at upgrade time, you can select Repository > Administration > Rebuild Clustered Indexes at any time to perform the rebuild.
5. Click Execute to begin the repository upgrade.

   The upgrade may take some time to complete. In the event of an upgrade failure due to network or permission problems, or insufficient disk space, you should restore the repository database from your backup version and retry an upgrade when problems are solved. If the upgrade fails because of the data in your database, then you should contact technical support for assistance.

6. [when upgrading from a repository before v16.1] If your repository contains branches, you are prompted to update your branches to the new implementation (see Post-Upgrade Cleanup for a Repository Containing Branches). Click OK to continue.
   Note: Depending on the complexity of your branch structure and the size of your repository, upgrading your branches may take a considerable time. If you click Cancel at this point you will leave the repository in a stable state, and can relaunch the upgrade at a later point by reconnecting to the repository.
7. [when upgrading from a repository before v16.1] If your current password does not comply with the default repository password policy, you will be prompted to change your password. Enter your new password (which must comply with all the rules listed in the dialog) and then click OK.
   Note: Administrators can control the restrictiveness of the password policy (see Core Features Guide > Administering PowerDesigner > Controlling Repository Access > Defining a Password Policy).
8. The Library Synchronization dialog opens to prompt you to synchronize the contents of your local library. Make any appropriate selections and click OK to perform the synchronization and complete the repository upgrade.
   For information about administering the library, see Core Features Guide > Administering PowerDesigner > Deploying an Enterprise Glossary and Library.
9. If you are using the repository proxy, then you must upgrade the proxy as well (see Installing the Repository Proxy).

• Post-Upgrade Cleanup for a Repository Containing Branches
  The new implementation of repository branches provides many improvements over branches in v16.0 and earlier, but if your existing repository contained branches, you may want to perform some post-upgrade cleanup of your updated branch structure or create a new repository and migrate all your active documents to it.