Cisco Cisco Administrative Workstation Technical References
Table 158: Indexes for Route Table
index_keys
index_description
index_name
EnterpriseName
nonclustered, unique, unique key
located on PRIMARY
located on PRIMARY
XAK1Route
SkillTargetID, ServiceSkillTargetID
nonclustered located on PRIMARY
X1E1Route
RouteID
clustered, unique, primary key
located on PRIMARY
located on PRIMARY
XPKRoute
Fields in Route Table:
Keys and Null Option:
Data Type:
Description:
Field Name:
NOT NULL
CHANGESTAMP
Incremented when the record is changed in the central database.
ChangeStamp
NOT NULL
DBCHAR
Deleted Flag. Stored as a character:
Deleted
• Y = Yes
• N = No
NULL
DESCRIPTION
Additional information about the route.
Description
AK-1 NOT NULL
VNAME32
An enterprise name for the route. This must be unique among
all routes in the enterprise.
all routes in the enterprise.
EnterpriseName
PK NOT NULL
DBINT
Unique identifier for the route.
RouteID
FK, IE-1 NULL
DBINT
Associated Service.SkillTargetID. Every route that terminates
at a peripheral should have a service.
at a peripheral should have a service.
ServiceSkillTargetID
FK, IE-1 NULL
DBINT
Foreign key from the Skill Target table that represents the
destination of the route. The destination is a Service, Skill Group,
Agent, or Translation Route.
destination of the route. The destination is a Service, Skill Group,
Agent, or Translation Route.
SkillTargetID
Route_Call_Detail Table
This table can become very large. Running custom reporting queries against it while it is on the
HDS can degrade performance. To optimize performance, extract the data from the HDS into
your own custom database on a separate server (one that is not used for other ICM/IPCC
components). Use only DBDateTime (date and time of the record that was written to the HDS
database) to perform the extraction. The table on the custom database can be indexed according
to the custom reporting needs.
HDS can degrade performance. To optimize performance, extract the data from the HDS into
your own custom database on a separate server (one that is not used for other ICM/IPCC
components). Use only DBDateTime (date and time of the record that was written to the HDS
database) to perform the extraction. The table on the custom database can be indexed according
to the custom reporting needs.
Central database only.
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
278
Chapter 2: All Tables
Route_Call_Detail Table