McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 398

↗ View in doc context
page
398
source
ucce/v15.0.1/db-schema-handbook/db-schema-handbook.md
chunk_id
ucce::v15.0.1::db-schema-handbook::db-schema-handbook::384

Table 329: Fields in Route Table Keys and NULL Option Data Type Description Name NOT NULL CHANGESTAMP Incremented when the record is changed in the central database. ChangeStamp NULL DBDATETIME Records the date and time when the record was added/updated. DateTimeStamp NOT NULL DBCHAR Deleted Flag. Stored as a character: • Y = Yes • N = No Deleted NULL DESCRIPTION Additional information about the route. Description NULL DBINT A unique identifier that identifies a department in CCDM/CCMP deployment. DepartmentID AK-1 NOT NULL VNAME32 An enterprise name for the route. This must be unique among 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. 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. SkillTargetID Route_Call_Detail This table is one of the tables in the Route category (see Route, on page 625). For more information about database rules of these tables, see Route Tables, on page 700. It gets populated on the central database. When Detailed Data Server (DDS) role is enabled on Administration and Data Server, this table gets populated on HDS database also. Whenever the system software receives a routing request, each row in this table records information about the routing request and the route the system software chooses for it. Therefore, the system generates a Route_Call_Detail record for every routing request it processes. Because this table grows larger in size, running custom reporting queries against it while it is on the HDS can degrade performance. To optimize performance, extract data from the HDS into your custom database. The custom database must be on a separate server and ensure that other Unified ICM or Unified CC Enterprise components do not use it. Use only DBDateTime (date and time of the record when written to the HDS Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 380 All Tables Route_Call_Detail