Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Reporting Services (and Cognos, Business Objects, and other BI reporting suites) generally have problems rendering reports that have hundreds of thousands of records or millions of records in the OUTPUT. Most of these systems don't have much of a problem aggregating the data into tens of thousands of records, but once you start going into the hundreds of thousands or millions, you will run into memory errors.</p> <p>My recommendation is to NOT use Reporting Services for reports that are hundreds of thousands of rows. No person is going to read all the lines in the report. Heck, most of the BI suites won't even output the report if you try to render to Excel due to the 65,556 row limitation. I would recommend using SSIS for large raw data dumps, Analysis Services cubes if you want to allow the user to do exploratory ad hoc slice and dice analysis in Excel, or find ways to break it into smaller, more relevant data that can be consumed by a human -- meaning aggregated or filtered to a few hundred or thousand rows.</p> <p>If you MUST use reporting services and you want to use it as a tool to get the data into Excel, then you could try rendering to CSV via a subscription. Again, I would recommend just building a SSIS package that does this instead since you won't have memory issues outputting multi-million row CSV files. But if you MUST use reporting services as the output tool, then minimize the memory cost by going with the least memory intensive rendering method.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload