Cisco Cisco E-Mail Manager Unity Integration Option Technical References
1-5
Cisco ICM/IP Contact Center Enterprise Edition Database Schema Handbook, Release 6.0(0)
Chapter 1 Introduction
General Concepts
The combination of FirstName and LastName is an inversion key for the Agent table. While this key
value is not necessarily unique, it is a convenient way to locate specific agents.
value is not necessarily unique, it is a convenient way to locate specific agents.
lists the types
of keys and the codes used for them in the ICM database.
In
the codes from
are used to identify key fields in each table. If a
table has more than one key of the same type, then numbers are attached to the codes. For example, if a
table has two alternate keys, then the fields that participate in the first are marked AK1 and the fields
that participate in the second are marked AK2.
table has two alternate keys, then the fields that participate in the first are marked AK1 and the fields
that participate in the second are marked AK2.
Each field is also marked as either NULL (meaning the NULL value is valid for the field) or NOT NULL
(meaning the NULL value is not valid).
(meaning the NULL value is not valid).
Reserved Fields
Some fields in the database are marked as reserved. This means that ICM software or the database
manager might use the field, but it has no external meaning. You must not modify any field marked as
reserved.
manager might use the field, but it has no external meaning. You must not modify any field marked as
reserved.
Table 1-1
Types of Keys
Key Type
Code
Description
Primary key
PK
Consists of one or more fields that have a unique
value for each record in the table.
value for each record in the table.
Alternate key
AK
A unique key that can be used instead of the
primary key to locate a specific record.
primary key to locate a specific record.
Foreign key
FK
A primary key from one table that appears in a
second table. A foreign key that establishes a
one-to-one relationship is always unique. A foreign
key that establishes a one-to-many relationship is
not unique.
second table. A foreign key that establishes a
one-to-one relationship is always unique. A foreign
key that establishes a one-to-many relationship is
not unique.
Inversion key
IE
A key that does not necessarily have a unique value,
but can be used to locate a group of records within
the table.
but can be used to locate a group of records within
the table.