Does anyone know if report definitions max rows to retrieve actually translates into a "fetch first 500 rows only" type of SQL or does Pega only process the first 500 results after all the results are returned from the DB?
The SQL seems to suggest the later, since there's no limiting SQL when looking at the SQL in pyReportContentPage.
Yes Greg, conceptually setFetchSize(int) can be better than setMaxRows(int) in terms of performance when we have huge data. I assume in pagination concept the user might navigate through the different pages frequently, so in this case the number of database round trips might become more if we use setFetchSize method. But i am not sure about the reason behind the usage of setMaxRows method for pagination concept using RD as i am not part of the engineering team. May be some Product expert in this domain might answer your queries Greg, as i had provided the above information by looking into the code.