sql server reporting services: I am running a large financial statement report (200,000 detail records
which are not all shown, just aggregated into the group structure), and I am
getting a System.OutOfMemoryException error on both my Dev box and
Production box.

The stored proc runs in less than 2 minutes in Query Analyzer.

Has anyone else run into this? What is the resolution?
Thanks

There is a known issue with PDF rendering with Reporting Services. It's
extremely slow and cumbersome and done all in memory. We had to
increase our RAM on our box from 2 GB to 16 GB just to get some of our
reports to run. We worked with MS for about 6 weeks on this. They
finally came back and said this product has not yet 'matured'.

Some things to try:
1) Only use CanGrow, CanShrink attributes on controls when absolutely
necessary.
2) Avoid using nested lists at all costs.
3) Return the least amount of data necessary from your SQL due to
memory issues.
4) Break reports up into smaller parts if possible.

James