Technical References

Central database only. Contains information about schedule import operations that have been
performed. The ICM software automatically creates an Import_Log row each time it imports
schedule information. The Primary Key (PK) is nonclustered.
Related table
Schedule (page 305) (via ScheduleID)
Table 111: Indexes for Import_Log Table
index_keysindex_descriptionindex_name
RecoveryKeynonclustered, unique, unique key
located on PRIMARY
XAK1Import_Log
DateTime, ScheduleID, TimeZoneclustered, unique, primary key
located on PRIMARY
XPKImport_Log
Fields in Import_Log Table:
Keys and Null Option:Data Type:Description:Field Name:
PK NOT NULLDBDATETIME
The date and time when the row was generated.
DateTime
NOT NULLVNAME32
The operation that was logged; for example Import or Edit.
LogOperation
NOT NULLDESCRIPTION
Indicates ‘Success’ or describes an error.
Message
AK-1 NOT NULLDBFLT8
A value used internally by the ICM software to track virtual time.
RecoveryKey
NOT NULLDBINT
The number of rows imported or modified.
RowsCopied
PK, FK NOT NULLDBINT
Identifies the schedule affected.
ScheduleID
PK NOT NULLDBINT
The time zone for the date and time. The value is the offset in minutes
from UTC (formerly called GMT).
TimeZone
NOT NULLVNAME32
The workstation from which data was imported.
WorkstationName
Import_Rule Table
This table is in the Blended Agent category (page 439). To see database rules for these tables,
click here (page 503).
Contains a list of all the import rules and their associated import lists. Use the Blended Agent
Configuration option within ICM Configuration Manager to modify Import_Rule records.
Note: If Outbound Option was not selected during setup, this table will contain no data.
Related tables
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
217
Chapter 2: All Tables
Import_Rule Table