The performance of the Experience Portal internal database degrades when 5 to 10 million records exist in any table. When you expect the number of calls or number of application-generated report records to exceed these values, you must use an external database.
The external database can be a new or existing database created in:
Note:
Avaya has tested Experience Portal with Oracle and SQLServer reporting databases containing approximately 50 million total records without any issues. Due to variances in database hardware and network performance, Avaya cannot provide a finite maximum number of records before the database reaches its practical limit. Scheduled reports are not subject to timeouts and can be used when on-demand report generation begins to time out. However, record insertions must be completed within 60 seconds to avoid web service time-outs and perpetual retries. Increasing the web service time-outs is not recommended. When insert time-outs occur regularly, Avaya recommends that you lower the record retention periods in the Report Data Configuration page. Fewer records mean faster insertions and faster report generation.
Important:
The administration and maintenance of the external reporting database and the periodic maintenance of the indexes is a customer responsibility.
