Setting up the Repository Database Server

The repository administrator must set up the repository on a database server running one of the supported DBMSs.

Note: When deploying to MS SQL Server, we recommend that you use a server that is not currently managing a high transaction load, since PowerDesigner performs long- running synchronous transactions during Check-In/Check-Out. 

In order to calculate the size required for your repository database, you need to estimate the number of models that will be stored and the period during which they will be developed. Repository models are stored as efficiently as possible, with only changed objects being re-saved.

An average model containing 100 primary objects (tables or classes) will have an initial disk size of 5MB and the size of its initial check in will be around 10MB. Assuming an average number of edits, each subsequent check in will add 10% to the size of the file, so that after an average development period of two months (40 working days) with one check in per day, the final model file size will be 10MB*1.140 or approximately 500MB. If your team will develop 20 models during the course of the year, you should allow 10GB of space for your repository database.

  1. Choose a server on which to install the repository. The server must be accessible to all those who will need to work with the repository.
  2. Install or obtain access to a DBMS suitable to store the repository tables. For this step, you have two options:

    • Install the authenticated version of Sybase SQL Anywhere 12 provided with PowerDesigner (see Installing SQL Anywhere).

    • Use your own DBMS

  3. Create an empty database to host the repository, with an administrator user who has full rights on all the tables. For instructions on performing this step with SQL Anywhere, see Creating a Database.
  4. On a client machine, with PowerDesigner installed, create a direct repository definition to connect to the new database by selecting Repository > Repository Definitions.

    For detailed information about creating repository definitions, see the Working with the Repository book.

  5. Enter an appropriate name to identify the repository, the user name ADMIN, and then press F4 to open the Select a Data Source window. Select the type of data source that you want to use to connect to the repository database. If it already exists, select it in the list; otherwise, click the Configure button and configure it as necessary.

    For detailed information about creating, configuring, and using connection profiles, see "Connecting to a Database" in Chapter 1, Getting Started with PowerDesigner of the Core Features Guide .

  6. Select Repository > Connect to open the Connect dialog. Select the name of the repository definition you just created and click OK to connect. A message box is displayed inviting you to install the repository. This will involve running a SQL script to create the necessary tables. Click Yes to continue.
  7. The read-only Repository Installation Script window opens. Click Execute to run the script and create the repository tables:


    Note: Although you cannot edit the script in the Repository Installation Script dialog, you can, nonetheless, modify the statements (for example, to add physical options) by copying the script to an external SQL editor, making the appropriate edits, and then connecting to the database to execute the script outside of PowerDesigner. The Separator list in the dialog lets you select the separator appropriate to your interpreter.

    When the repository has been successfully installed, a final message "Repository installation completed" is displayed in the Output window. In the repository Browser, the root of the repository tree now displays the repository name, the repository user and the current branch (MyBase::ADMIN::<Default>), and is ready for use.

Notes:

  • By default, database tables are owned by the user who creates them. Each repository user should either use the same database user name and password to access the repository, or have an account that gives them full rights over all the tables.

  • Repository installation may occasionally fail due to network problems, insufficient disk space, or permission problems, and you can choose whether to ignore the errors or abort the installation. We recommend that, if you are unsure, you abort the installation, and start again.

Parent topic: Installing the Repository