Chapter 4 Connecting to the Repository
When you connect for the first time to a database that will store the repository, you initialize the repository and create the tables: this step is called the repository database creation.
Caution
Repository database creation is not possible using the repository proxy connection, you must use a direct ODBC connection instead. One person will create the repository through this direct connection, then other users will be able to access it through the proxy.
When the tables are created, they are owned by the user logged to the database. The name and password of this user appear in the Database group box of the repository definition dialog box. Each repository user should use the same user name and password to access the database tables:
Whatever the repository user login name you have specified in the repository definition dialog box, the first time you connect to the database you are connected as ADMIN. This is to let you create the repository tables, define users and groups of users, define their rights, and perform all sorts of administrative tasks that belong to an administrator profile.
If you disconnect and reconnect to the database, the default login name and password, as defined in the repository definition dialog box, are used:
Initialization and upgrade statements appear first in the Repository Installation Script window. You can use this window to browse the statements.
Read-only window
The Repository Installation Script window is read-only. You cannot edit any statement.
You can modify the default statements for example add physical options. You should also make sure that the database you create for the repository supports transactions, and if need be modify the default statement accordingly: for example, in Informix, you must add the "WITH LOG" option.
To modify the default statements you have to copy the text, and paste it in a script interpreter. The Separator list lets you select the separator that corresponds to your interpreter. When you change separator using the Separator list, the script automatically displays this change. You then have to click Cancel in the Repository Installation Script window, then modify and execute the statements with your script interpreter.
Repository installation may fail for the following reasons:
In case of failure, a warning message is displayed with the following buttons:
It is recommended to drop repository tables and restart installation in case of network problem, insufficient disk space, or permission problem.
Caution
Do not drop repository tables in case of conflicts with existing objects as drop process may remove tables with identical names from other applications in the database. Also, avoid using the Abort option when conflicts with existing objects occurs as Abort option also drops repository tables and tables with identical names.
In case of conflicts with existing objects, you should:
Model versions are usually stored as a set of differences from the previous version. They share the unmodified object versions with the previous version. This does not apply to the first versions (v1 or v1.1), or the baselined versions, that are both stored as a set of fully independent objects. As a rule of thumb, such an independent version takes in the database twice the size of the corresponding model stored in an XML file.
Suppose a design team is working on a 5-MB model. After one year, and an average of 8 consolidations / week, there are around 400 versions in the repository. The size of the baseline version is 10 MB. The size of each version is around 5% of the total size of the model, so the total volume of versions is around 200 MB. You will need more than 210 MB to store the repository database.
| Copyright (C) 2006. Sybase Inc. All rights reserved. |
| |