Database Configuration

You use the Database Configuration application to create or change objects and attributes, and to customize the database. An object is a self-contained software entity that consists of both data and functions to manipulate data. Most applications are associated with one main object and other related objects.

When you use the Database Configuration application, you interact at the business object level. Internally, the application determines the actions to take on the database tables to support the needs of business objects.

A database table can store several objects, each object having different business rules. For example, the TICKET table defines Incident, Problem, and Ticket business objects, which are defined as database views. In addition, a business object (view) can span more than one database table. Views represent objects that can span multiple tables.

With the business object layer, the system tables that must not be modified are not editable on the user interface but you, an administrator, can view them.

When changing the database, for example, when creating or deleting objects, attributes, or indexes, changes are stored in secondary tables. The changes do not take effect until you configure the database. It is important to back up your data before configuring the database.