Tuning the Database Schema of an Information Model
The repository engine stores data in a relational database. When you add an information model, the repository engine enlarges this database by creating new tables and columns to accommodate your tool information. Generally, each interface corresponds to a table, and each property corresponds to a column. When you populate your information model, the repository engine inserts rows into these tables.
You have some control over the database schema that accommodates your tool information. For example, you can:
- Use a single table to contain the interface-specific properties of more than one interface.
To do this, set the TableName property for each interface definition object to the same name before you commit the transaction that is used to create your information model.
- Create an additional index for a table.
To do this, open the database directly and use the SQL CREATE INDEX command after you commit the transaction that is used to create your information model.
Note You cannot completely control the database schema. In particular, each table must include the columns IntID, Z_BrID_Z, and Z_VS_Z, and must define the primary key on those columns. Furthermore, you cannot drop columns that your information model uses to store properties.