I am testing the 2008 version of Reporting Services hoping this is will allow us to render reports with ~200k rows. We are currently running Reporting Services 2005 in production and find that reports with even 100k rows will report out of memory exceptions. In Brian Welckers weblog http://blogs.msdn.com/bwelcker/archive/2007/12/04/everybody-why-leave-iis.aspx he states that For example, RS 2008 has a new on-demand processing model to ensure that no report executions will run out of memory. It does this by paging and releasing allocated memory to the disk when it gets memory pressure notifications. This would have been very difficult to implement using the IIS hosting model. For example, RS 2008 has a new on-demand processing model to ensure that no report executions will run out of memory. It does this by paging and releasing allocated memory to the disk when it gets memory pressure notifications. This would have been very difficult to implement using the IIS hosting model. I am running 2008 where I am only running a single report that I would expect to retrun 180 k rows of data and still get the Out of Memory Exception. Has any one else see this fixed in reporting services 2008. Additionally I dont see anything that would need to be included in the RSREPORTSERVER.CONFIG to accomplish this. Error in log: processing!ReportServer_0-1!1390!09/05/2008-12:45:04:: e ERROR: An exception has occurred in data source 'SP_RPTPKG_COMPENSATION_COST_ACCRUAL_RS'. Details: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. Has anyone seen this error in the new environment or seen an improvement in the number of rows reporting services can render since upgrading to 2008.

Cumulative Update #1 for SQL Server 2008 will be available soon via Microsoft Support. It contains a minor change that should resolveyour issue (in which case the GC doesn't seem to keep up with reclaiming the freed memory by RS). Internally, we have been running reports with 10+ million rowssuccessfully. -- Robert

Do you have any idea when this will be made available on the download site ? Is there any way to get and advanced copy for eval / testing. thanks again.

Are you withDeltek? I think there is already an offline discussion between you and Microsoft Support on this topic. -- Robert

I work for Computershare we were part of the SQL Server 2005TAP for SP 2 working with Xiaoyu Li. We would be happy to do the same with this upcomming release. Like I have said before, we experience alot of pain in production when we cannot produce our reports containing > 100k rows. Anything you can do to expedite the delivery of this version would be very much appreciated. thanks again for the quick response.

Is the out of memory issue fixed if I use Reporting Services 2008 against a SQLServer 2005 or 2000 database please? I have reports of approx 150,000 rows and I get out of memory when I export to Excel. Thanks a lot- I'm on the critical path with this :-) Tom.

I would think not, but would yield to a response from MS. But the fix appears to be comming in the next sp of sql server 2008 and doesn't have much to do with the source db from which data is pulled from. We use oracle, but I think that point is moot.

The Excel binary format (BIFF) generated by Reporting Services has a general restriction of 64K rows maximum per worksheet - so depending on whether your report has page breaks, you might not be able to export to Excel due to that Excel file format row limit. As far as RS 2008 is concerned, cumulative update #1 was released today (http://support.microsoft.com/kb/956717/en-us), which should resolve Alan's problem. -- Robert

I am more concerned about the out of memory exceptionsthat exist in rendering all output formats. I will download the patch and post my results to this thread. thanks.

I have tried to run a report from report mgr that returns ~ 420k rows and am no longer getting out of memory exceptions, but now get a timeout situation , even with the execution timeout set to infinate. runningjobs!ReportServer_0-5!68c!10/01/2008-12:35:26:: i INFO: Adding: 1 running jobs to the databaselibrary!ReportServer_0-5!564!10/01/2008-12:36:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database., ;session!ReportServer_0-5!564!10/01/2008-12:36:00:: e ERROR: Sql Error in GetSnapshotData: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

I'm having the same out of memmory exception,running concurrently 2 instances of the same report, which retrieves from sql around135k rows and thenafter somecolumn grouping transforms them into a 3 sheets excel, with 2k rows per sheet. I applied the latest Cumulative update 3, also I played around withMemoryThreshold,WorkingSetMaximum,WorkingSetMinimum but no improvment.is there an workaround to solve this problem or not? Cause restricting the number of concurently reports to 1 is not really a good solution.laurentiu

Sorry I can't give an answer but reporting services has been running out of memory for years, and each time we're told "it's fixed in the next release / patch / whatever". I got burned so badly on this a few years ago I've still got the scars. And I looked like a muppet to management when the next version didn't fix the issue at all.

We are on one of the latest versions of SQL 2008 R2 and still have this problem. It's obvious that MS does not have a clue about how to fix it. This is only one of many things MS does not have a clue about. Rich

We are on one of the latest versions of SQL 2008 R2 and still have this problem. It's obvious that MS does not have a clue about how to fix it. This is only one of many things MS does not have a clue about. Rich It's shameful. If they said "we're not going to, or can't fix this" then at least people could make a decision. But this "the next release fixes it, really, please commit to us" bull has been going on for 5 years now.

I take it this is still an issue? I'm running a report which returns over 500,000 rows and getting the SSRS out of memory exception. (and before anyone pipes up with "why are you returning that many rows, filter the data!" we are returning a large dataset for compliance reasons...it's the business requirement)

For the record I jumped the gun with my last post. I only get the out of memory exception when trying to preview the report through the BIDS report builder. When I deploy the report and run it through the web portal it's fine. I watched the performance monitor while the report was running and I could see the memory peaking and then dropping as it was released. Well done Microsoft.

I'm getting 'system.OutOfMemoryException' on our companies SSRS server... SSRS version: - Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) What version are you running? Do you think an upgrade to R2 will resolve this issue or are there CU's that will help? getting desperate any help that anyone can offer would be greatly appreciated. dzinni