ReportBuilder has been tested to handle large (multiple thousand) page reports. I would suggest creating your report as you normally would and seeing if it runs to your expectations. If there are problems with memory, speed, etc., we can try to pursue other options.
Note that most speed problems dealing with larger reports are usually due to slow data access or network access.
I'll add to Nico's comments: if speed of the system is essential, use JIT pipelines backed up with class structures, not datasets. In lots of years of working with them, I find datasets slow.
I have a in house developed pipeline for QuantumGrid. It has worked nicely with reasonable amount of data. I will look into it if I have performance problems. Every process (fetching, generating, spooling etc) start to get slow due to the amount of data. But my main goal is to achieve a linear increase in the worst case
Comments
ReportBuilder has been tested to handle large (multiple thousand) page
reports. I would suggest creating your report as you normally would and
seeing if it runs to your expectations. If there are problems with memory,
speed, etc., we can try to pursue other options.
Note that most speed problems dealing with larger reports are usually due to
slow data access or network access.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
pipelines backed up with class structures, not datasets. In lots of years of
working with them, I find datasets slow.
--
Ed Dressel
Team DM
I have a in house developed pipeline for QuantumGrid. It has worked
nicely with reasonable amount of data. I will look into it if I have
performance problems.
Every process (fetching, generating, spooling etc) start to get slow due
to the amount of data. But my main goal is to achieve a linear increase
in the worst case