Cisco Cisco IP Contact Center Release 4.6.2 Maintenance Manual

Temporary Database

Because real-time or historical data are read frequently by the reporting clients that might have
complex queries, the SQL Server uses the tempdb database to store the data result set before it
is given to the connected clients. For better performance, set this database to Auto Growth.

Historical Data Server

Administration & Data Servers need to access historical data (15-minute and half hour data,
call detail, and so forth). The system software normally stores historical data in the central
database on the Logger, as well as on the Administration & Data Server that acts as the Historical
Data Server (HDS).

One Administration & Data Server at each admin site is an HDS machine. The Central Controller
forwards historical records to the HDS machine for storage in a special local database (awdb).
Other Administration & Data Servers at the local site can retrieve historical data from the HDS
machine without having to access the central site (see the following figure).

Figure 10: Historical Data Server Architecture

To set up an Historical Data Server, you must configure the Logger to perform historical data
replication. You must also configure an Administration & Data Server to be an Historical Data
Server. You can use the ICMDBA tool to create an HDS database, then use the Web Setup tool
to add an Administration & Data Server with an HDS role.

Small to Medium Historical Data Server Deployments

Note: Before reviewing this section, review the Cisco Unified Contact Center Enterprise 8.x
Solution Reference Network Design (SRND) at 

about small to medium deployments.

Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x