Incremental loading limits the amount of data that is returned for each database query. This allows users to load reports incrementally, starting with a small set of rows and adding more in steps as desired.
Incremental loading can shorten the amount of time it takes a report to load and be usable. It can also help reduce continuous load on a database which may improve load balancing performance.
To enable it, set Admin Console > General > Database Settings > Row Limit Step Size to a value greater than 0. This value sets the initial number of rows returned when the report is first executed, as well as the number of rows returned for each subsequent query.
We recommend setting Row Limit Step Size to a minimum of 1000.
The step size can be overridden for with a smaller value at the report-level with the Advanced Report Designer’s Report Viewer option Report Row Step Limit.
Choosing a Row Limit Step Size that allows most reports to avoid reaching the limit entirely is ideal since truncated results can affect report accuracy. Summary data may not be accurate if not all of the pertinent rows are available for aggregation. Another consideration is performance. If there are a lot of slow running reports due to the amount of data being returned, then the need to balance between report completeness in the first execution vs performance by limiting the number of rows returned will need to be considered. Each environment is unique, so the 1000 row recommendation can be used as a starting point and then fine tuning applied.
With incremental loading enabled, when an ExpressView is run or a report is run in the Report Viewer (the interactive toolbar must be enabled), the report will only query the first number of rows specified in the configuration setting.
If there are fewer rows than the full data set:
- (v2021.1+) a link displays on the toolbar with the message Showing X Results. Click the link to load more data:
- Load X more Records — get the next number of data rows and add them to the existing report
- Load All Data — get the remainder of the data set
- (pre-v2021.1) an alert icon displays on the toolbar with the message “Truncated results displayed” unless the report qualifies for Infinite Scrolling.
Click the icon to retrieve more data. Choose from:
- Generate +number to retrieve the next number of rows and add them to the report. (The number is determined by the Row Limit Step Size setting).
- Generate All to get the full data set.
Exporting a truncated report from the Report Viewer generates a file with only the existing rows.
Incremental loading has no effect for Dashboards, Chained Reports, or Scheduled Reports. Exporting from the Report Tree and Advanced Report Designer is not affected by incremental loading.
Infinite Scrolling v2018.1+
With Incremental Loading enabled, in certain conditions, scrolling or paging through the Report Viewer will cause additional rows to be loaded automatically instead of needing to click the Truncated Results Displayed alert icon each time.
When a report qualifies for infinite scrolling, the Truncated Results Displayed alert icon and the Report Viewer’s interactive sorts and filters dock will be hidden.
Conditions for Infinite Scrolling
Infinite Scrolling requires reports to be designed in a certain manner. If the conditions are not met, users will need to manually step through the rows instead by clicking the icon.
To qualify for infinite scrolling, reports must have:
- a visible Detail section ,
- at least one Sort,
- utilize a data source that supports range selection, such as Oracle, MySQL, DB2, Informix, Microsoft SQL Server, or PostgreSQL.
A report that contains any of the following will be disqualified from infinite scrolling:
- interactive sorts or filters (sorts and filters in the Report Viewer’s interactive dock)
- Top N filters
- a CrossTab
- collapsible groups
- cross-source or Cartesian joins
- in-memory aggregate functions (e.g. RunningSum), custom functions, or server events that use the full data set (e.g. OnDataCombined).
- a Row Limit Step Size setting that returns less than one full page of data
The method used to construct the range limiting SQL statement depends on the Data Source, and can be customized by editing the dbconfigs.json and setting the
"RowRangeMethodString" property for each source. See Constants and Enumerators: wrRowRangeSqlMethod for valid values.