Using Report Definition for custom aggregation, any limitation? E.g. 10K records?
Hi,
I am using Report Definition to get a list of records that satisfy a given criteria for my custom aggregation and computation (by looping through this list). This is not meant for displayed in the Report Browser.
So far, there is no issue, but I would like to know whether the number of records returned would be truncated? E.g. if the number of returned records is 20000 (for example).
I understand that there is a "Maximum number of rows to retrieve" in the Data Access tab, is there a limit to this entry? Or is this capped by the "pyMaxRecords" in the DSS?
If I were to set "Maximum number of rows to retrieve" as 0, would it enable me to get all the data for iteration?
Thanks and regards,
Jacky
Pegasystems Inc.
IN
Hi,
Thanks for posting on PSC.
There would be performance overhead if you're retrieving all the records in memory or to the clipboard(It will cache it).
As per my knowledge, there isn't any limitation for the "Maximum number of rows to retrieve" in the report definition.You can retrieve all records.
It can be configured from "Reporting: Settings" landing page as well. Navigate, Designer Studio->Reporting->Settings->Settings.
Tune it according to your requirement, it will be applied at the application level. Make sure, you provide tuned "Maximum Elapsed time" in comparison with the number of rows to be retrieved, as database transaction would fail if SQL runs for more time than configured and end up throwing an error.
Hi,
Thanks for posting on PSC.
There would be performance overhead if you're retrieving all the records in memory or to the clipboard(It will cache it).
As per my knowledge, there isn't any limitation for the "Maximum number of rows to retrieve" in the report definition.You can retrieve all records.
It can be configured from "Reporting: Settings" landing page as well. Navigate, Designer Studio->Reporting->Settings->Settings.
Tune it according to your requirement, it will be applied at the application level. Make sure, you provide tuned "Maximum Elapsed time" in comparison with the number of rows to be retrieved, as database transaction would fail if SQL runs for more time than configured and end up throwing an error.
Hope it helps you to configure your requirement, kindly notify by marking this post as answered/helpful if it does.
Regards,
Asif