One report element equals running the Skill Status report with a three-second refresh rate and retrieving 100 rows of data.
You can access the report from .
The Skill Status report includes the following two queries:
Query data1: select csplit.INQUEUE + csplit.INRING, csplit.OLDESTCALL, csplit.EWTTOP, csplit.EWTHIGH, csplit.EWTMEDIUM, csplit.EWTLOW, SKSTATE from csplit
Query data2: select cagent.LOGID, cagent.LOGID, cagent.AUXREASON, cagent.AWORKMODE, cagent.DIRECTION, cagent.WORKSKILL, cagent.WORKSKLEVEL, cagent.AGTIME, cagent.VDN, cagent.AWORKMODE from cagent
Query data1 returns one row with seven fields. One field uses a synonym lookup.
Query data2 returns ten fields. In this example, the query returns 100 rows.
Six fields use synonym lookups, and two fields use keyword lookups. Synonym and keyword lookups are approximately twice as resource-intensive as plain data fields.
Adding a summary query increases the load on the CMS.
If you run the Skill Status report with a three-second refresh rate and the report returns 200 rows, it counts as two report elements.
Integrated queries place a higher load on the server when they start. However, after initialization, they retrieve data similar to real-time reports except at interval, day, and start-of-day boundaries.
Historical reports impact server performance when you run, refresh, or restart them.
