Database dictionary

Service Manager maintains a logical view of your RDBMS tables and columns in the database dictionary. The database dictionary describes each table and column in your system and how they are mapped to logical entities within Service Manager. The Service Manager applications use the logical definitions in the database dictionary to query and manage the actual records in your RDBMS. You must create a database dictionary record for each table and column in your system.

Every time you add tables and columns for Service Manager to your RDBMS system, you must also create database dictionary records describing these new items before Service Manager can make use of them. The best practice we recommend is to create the database dictionary records first, and then have Service Manager create the back-end tables and columns for you automatically. Some environments, however, do not permit Service Manager to add or update records in the back-end RDBMS.

In restricted-access RDBMS environments, Service Manager can create database definition language (DDL) describing the changes proposed by your database dictionary records. The RDBMS administrator can then create the necessary tables and columns for Service Manager . After the RDBMS has the necessary tables and columns, the Service Manager administrator can then update the database dictionary records to map to the actual RDBMS objects. To simplify the mapping process, Service Manager administrators can also import columns from an RDBMS into a database dictionary record.

You can access database dictionary records either from the System Definition utility or from the database dictionary form. Both utilities require having the SysAdmin capability word or its equivalent. We recommend using the System Definition utility to create database dictionary records if Service Manager has table create-alter-drop-rights to the RDBMS. If your environment restricts access to the RDBMS, we recommend using the database dictionary form to create the initial null mappings and then update the database dictionary by importing the RDBMS tables and columns.

To provide Service Manager with table create-alter-drop-rights to your RDBMS, you must add the RDBMS connection parameters to the server configuration file (sm.ini). The RDBMS user name you provide Service Manager must at least have add and drop access rights. We recommend you grant the RDBMS user owner rights over the database so that Service Manager can manage the data as needed.

To have the server create DDL for database dictionary changes, you must add the sqlddllogging and sqlddldirectory parameters to the server configuration file (sm.ini). The server creates one DDL file for each logical table in the database dictionary. For example, the file prosummary.ddl contains DDL for changes made to the probsummary database dictionary record, which in turn, maps to the physical tables such as PROSUMMARYA1, PROSUMMARYM1, and PROSUMMARYM2 in your RDBMS. You can enable exporting to DDL independently of providing Service Manager with table create-alter-drop-rights to the RDBMS. You may want to export all RDBMS changes to DDL to keep a log of changes to your RDBMS.

Related topics

Data persistence
Automatic update of database dictionary records
Automatic update of RDBMS data when database dictionary records change
Database dictionary data types
Database dictionary records

Create a database dictionary record by importing RDBMS columns
Create an active database dictionary record
Create an inactive database dictionary record
Enable DDL logging of database dictionary changes
Import RDBMS columns into an existing database dictionary record