Technical References

Table 158: Indexes for Route Table
index_keysindex_descriptionindex_name
EnterpriseNamenonclustered, unique, unique key
located on PRIMARY
XAK1Route
SkillTargetID, ServiceSkillTargetIDnonclustered located on PRIMARYX1E1Route
RouteIDclustered, unique, primary key
located on PRIMARY
XPKRoute
Fields in Route Table:
Keys and Null Option:Data Type:Description:Field Name:
NOT NULLCHANGESTAMP
Incremented when the record is changed in the central database.
ChangeStamp
NOT NULLDBCHAR
Deleted Flag. Stored as a character:
Deleted
• Y = Yes
• N = No
NULLDESCRIPTION
Additional information about the route.
Description
AK-1 NOT NULLVNAME32
An enterprise name for the route. This must be unique among
all routes in the enterprise.
EnterpriseName
PK NOT NULLDBINT
Unique identifier for the route.
RouteID
FK, IE-1 NULLDBINT
Associated Service.SkillTargetID. Every route that terminates
at a peripheral should have a service.
ServiceSkillTargetID
FK, IE-1 NULLDBINT
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.
SkillTargetID
Route_Call_Detail Table
This table is in the Route category (page 447). To see database rules for these tables, click here
(page 507).
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.
Central database only.
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
278
Chapter 2: All Tables
Route_Call_Detail Table