Manual
Reporting Best Practices
This section contains the following topics:
•
CPU Intensive Reports, page 81
•
Filtering Data to be Stored in the Database, page 82
•
ECC Variable Security, page 82
•
Writing Efficient SQL when Creating Reports, page 83
•
Database Sizing Issues, page 83
•
Database Backup and Recovery, page 84
•
Only Use Reporting Users when Querying the Database, page 84
•
Informix, Operating System Time, and Local Time, page 84
•
Assuring Accurate Time Stamps for Reporting and Logging, page 84
•
Passwords, page 84
•
Joining Data with an ICM HDS Database, page 85
•
Joining Unified CVP and SQL Server Data, page 85
•
Reporting Isolation Level, page 85
•
Database Retention Settings, page 85
•
Purge and Backup Database Maintenance Tasks, page 85
•
Zero Duration Calls and Writing Reports, page 86
CPU Intensive Reports
Do not run CPU intensive reports off the database while the database is receiving data.
Note: Reports become more CPU intensive as the complexity associated with producing the
report from the information available in the database increases. There is no sharp dividing line
between intensive and non-intensive reports. The system performance must remain within the
guidelines defined in the Cisco Unified Customer Voice Portal (CVP) Release 4.0 Solution
Reference Network Design (SRND) document.
Reporting Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
81
Chapter 7