Concurrent queries in batch reports versus interactive reports

In general, to render reports more quickly, you should run them in a non-interactive mode instead of in interactive mode.

The concurrent query manager processes queries starting from the last query of the report and works its way to the first. When reports are rendered in a non-interactive mode, the Report Server main thread will run the first queries. It will also start to use available helper threads to start queries associated with layouts it will move to. By starting those queries, data can be available to render instead of waiting for the query to be executed at that time.

The same strategy is also used for interactive reports. However, a report design may include several page layouts which a user never navigates to. In effect, the system may have run several queries that will never be rendered as the layout is not required. Interactive mode should be enabled only if interactive reports tend to be completely consumed, such as single-page layouts. It should not be enabled if interactive reports tend to be used to view just a few pages of many.