Cisco Cisco IP Contact Center Release 4.6.1 Maintenance Manual

The central Unified ICM database resides with the Logger itself. If the Logger is duplexed, each
physical Logger has its own copy of the database. If the Logger services multiple customers,
each machine has a separate database for each customer.

The name of the central database has the form inst_sideX, where inst is an up-to-five-character
instance name and X indicates the side of the central controller (A or B). For example, the central
database for cus01 on the Side A Logger is named cus01_sideA.

Database Sizing and Creation

When you first set up the Logger software on a machine, you must also create the central
database. If you set up multiple Loggers (for multiple customers), you must create a central
database for each instance.

Before creating the database, you must determine how much space it requires. The size of the
database depends on a number of factors, including the size of your configuration, the expected
call load, how long you want to retain historical data, and the number and size of configured
ECC variables.

Use the Database Sizing Estimator applet to estimate the database size, based on the expected
usage.

Note: ECC variables add impact for each Route Call Detail (RCD) and Termination Call Detail
(TCD) generated, which results in a large impact, so make sure this information is accurate.
From this information, the Database Sizing Estimator applet can more accurately determine the
impact of the specified ECC variables on the database size for the given number of retention
days (usually 14 days for a logger database; larger number for HDS databases).

To prevent the database from growing indefinitely, old records are automatically purged from
the historical tables on a regular basis. You can work with your Unified ICM support provider
to decide how long you want to retain historical data in the central database.

For specific information on sizing and creating the database, see Chapter 4, "

Optimization Tips for SQL Server 2005 with SP3

Note: Unified ICM/CCE/CCH Release 8.0(1) supports SQL Server 2005 with SP3 for new
installs and upgrades. Systems with SQL 2000 must upgrade to SQL 2005 SP3 before upgrading
Unified ICM.

SQL Server database files can be configured to grow automatically, using the Autogrow feature.
This eliminates many problems that occur when logs or databases run out of space.

In the event that the Unified ICM database is undersized or there is an unplanned increase in
the data stored in the database and the Unified ICM processes cannot purge the data to maintain
the maximum database size, the autogrow option automatically expands the database when
additional space is required.

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