Monday, January 28, 2013 4:53 PM
I am running large SSRS reports in a local mode via the VS 2010 ASP.NET Report Control AND SSRS 2008 reports via the Report Server.
These reports have thousands of pages and thousands upon thousands of records.
Can anyone offer me any advice on how to bypass this issue in both scenarios ? I was under the impression this iteration of SSRS would eliminate the memory issues that plagued earlier SSRS versions.
Wednesday, January 30, 2013 12:32 PMModerator
To make report performance, please refer to the following suggestions:
Suggestion 1: Check the configuration settings for memory in the RSreportserver.config file. By default, the WorkingSetMaximum setting doesn’t appear in the RSReportServer.config file. If it has been change, remove it or change its value to be a larger integer value. For more information, please see: Configuring Available Memory for Report Server Applications
Suggestion 2: Redesign the report. To do this, please refer to the following methods.
- Return less data in the report queries.
- Use a better restriction on the WHERE clause of the report queries.
- Move complex aggregations to the data source.
- Include fewer data regions or controls in the report.
- Use a drillthrough report to display details.
- Add page breaks where it makes sense.
- Avoid complex expressions in the Page Header or Footer which force all pages to be processed
- You may receive the "System.OutOfMemoryException" error message when you use SQL Server Reporting Services
- Troubleshooting Reports: Report Performance
Hope this helps.
TechNet Community Support
Thursday, January 31, 2013 3:35 PMAny suggestions on how to catch the memory exception in either case? The expection seems to be thrown after it finshes executing the code.