System.OutofmemoryException

Question

System.OutofmemoryException

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply

philcart SSC-Forever Points: 47796 More actions · Answer 1

I still go back to my original posting,

"If the report is many, many pages long, then thinking logically, is the report useful? Would it be better seperated into smaller reports?"

I mean are the consumers of the report actually going to wade through all 200+ pages of the report?

We had a report on our old reporting system that went to 400+ pages and took over an hour to produce. After sitting down with the users and seeing how they actually used the report we discovered that they were only interested in items over a certain value. When they received the report on Monday they spent the better part of the morning going through the report and highlighting each item they had to follow up.

We applied some basic criteria to the report and now it's only 2 pages long and is produced in seconds. They're even thinking about leaving the browser window open and not printing the report. The idea of re-running the report throughout the week and having verified/fixed items removed from the list is also a novel idea for them.

--------------------
Colt 45 - the original point and click interface

Dave Klug SSCertifiable Points: 5811 More actions · Answer 2

I was having the same issue. Users were running large reports and the server was tyhrowing out of memory excpetions. Only way to resolve was to replace the server.

Syed Asim Rizvi Ten Centuries Points: 1162 More actions · Answer 3

By default RS uses maximum of 60% of available memory. You can change this setting (if you wants to) by changing value of

<

MemoryLimit>60</MemoryLimit>

in RSReportServer.config file (resides in \MSSQL\Reporting Services\ReportServer folder).

This might help.

Let us know.