If the report is data intensive, best practice is to set it up as a report and deliver it to the Inbox on the Reports tab. Do not set this up as a query report, because query reports are run in real time against the PACE Application server. As a result, when numerous users run the query report during business hours, the response time before the results are displayed may exceed a few minutes. Consider the following to help decide when to use an Inbox report vs. a query report.
Number of rows of data returned: The more rows of data, the longer execution takes. Eagle’s recommended row limit is the default 5000 rows as displayed in Portal Administration. If you exceed this limit, you should consider using an Inbox report and not increasing the limit.
Number and type of columns of data being returned: Generally, making more columns of data available reduces the maximum amount of data one would want to return. More advanced field types may take longer to fetch than pure database fields.
Web server/server timeout settings: If the amount of data being returned exceeds timeout settings, the data is not returned quickly enough to avoid getting a timeout message.
Network transfer speed: If most of your users are accessing the query reports over slow network connections, the amount of data you should make available via Portal Query reports is less than if all users have local network access over a high speed connection.
Beware of indexes containing large numbers of Portfolios, as they may run for more portfolios than initially expected.
Add Comment