Technical References

Keys and Null
Option:
Data Type:Description:Field Name:
• Y = Partitioning is enabled.
• N = Partitioning is not enabled.
Note: (1) Changing this property will cause ALL person login
names in the database to be changed appropriately. (2) It is
possible that not all person records can be converted from case
sensitive to not case sensitive or the reverse. This can happen if
changing the case causes a name conflict with other login names
in the system.
ICR_Instance Table
This table is part of the Script category (page 451). For database rules, click here. (page 509)
Each row defines an ICM instance. For a Network Applications Manager (NAM), you should
configure an instance for each associated Customer ICM. Use ICM Configuration Manager to
create, update, or delete an ICM instance.
Related tables
Application Gateway (page 60) (via ICRInstanceID)
Customer Definition (page 153) (via ICRInstanceID)
ICR Node (page 214) (via ICRInstanceID)
Table 106: Indexes for ICR_Instance Table
index_keysindex_descriptionindex_name
EnterpriseNamenonclustered, unique, unique key
located on PRIMARY
XAK1ICR_Instance
NetworkICRInstanceIDnonclustered located on PRIMARYXIE1ICR_Instance
ICRInstanceIDclustered, unique,primary key located
on PRIMARY
XPKICR_Instance
Fields in ICR_Instance Table:
Keys and Null Option:Data Type:Description:Field Name:
NOT NULLCHANGESTAMP
Incremented when the record is changed in the central database.
ChangeStamp
NULLDESCRIPTION
Any additional information about the instance.
Description
AK-1 NOT NULLVNAME32
An enterprise name for the instance. This name must be unique
for all ICM instances in the enterprise.
EnterpriseName
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
212
Chapter 2: All Tables
ICR_Instance Table