I have a dataset with 300,000 records and I'm getting the following error with MS Reporting Services. "An error has occurred during report processing. Exception of type System.OutOfMemoryException was thrown. any help with this would be highly appreciated.

Unfortunately, Reporting Services has some memory limitations in the current (SQL 2K and SQL 2K5). Because we support things like dataset aggregates (you can have sum(x) on the first page of your report), we materialize the entire dataset. Some things you might try: Do you need the entire data set displayed in the report or could you do some grouping / aggregation in the query? Could you break up the report into smaller, parameterized reports? Could you give RS more memory by moving it to it's own server or even moving to the 64 bit version? For the post-Yukon release, a top priority is enabling these large data reports but you may have to work around it for now.

I am having a similar problem with large data amounts. My reporting server is a Dual Xeon 3GHz machine with 2.5GB RAM and still has issues. What I find is that the reportviewer object is not releasing memory after the reports are generated, viewed and closed. It recycles the application several times if I try to do an export to excel. Is there any way to be sure to dispose of the memory being allocated by the reportviewer? I can generate one report, close it, wait, open another, and the memory allocation just keeps growing and growing. Any help is appreciated.

I seem to be having a similar problem with a Xeon and 4Gig of memory. In my case, after the out of memory error happens, remote connections stop working stating that there is insufficient memory. In other words I can't even run a select statement in Management Studio after it hits the memory error. I have to restart the SQL Service. HELP!!!

First off. A human does not look at 300,000 records. Most of the time I have seen this it has been to export to Excel. When exporting to Excel export as CSV ASCII (although I don't think Excel can handle more that 64,000 records). Note that this is with records returned, not records in the base table. I go against tables with 150 million records but I only return the data needed. I suggest looking at design drill through reports to limit the data.

Is this still a problem with Reporting Services? We are having a similar problem with .net choking on large data sets and were considering using Reporting Services as an alternative. Is Microsoft an enterprise player or not? We are required to periodically return several hundred thousand rows from SQL Server. I'm tired of being told that is a design problem. Unfortunately when our client says he needs to print a detail report from his general ledger for his auditor we don't have the luxury of telling him Microsoft doesn't think he needs that large of a report. If he can't get the data he needs from us, he'll be happy to go down the street to get it (read Oracle). If I can't serialize it through .net or get it out of Reporting Services, how am I supposed to extract large data sets from SQL Server? Will 64 bit processors and multi-GB ram implementations help? Thanks.

I am facing the same problem also. I have an area chart that needs to plot more than 200,000 records and I am facing the problem "Internet Explorer cannot display the Webpage after waiting for 30minutes". How come RS never looked at this kinds of situations?Can anyone help me on this? Thanks

We have the similar problem. We can not make an argument with customer that they do not need that large report even though we are with Microsoft that they should only read a smaller report. Does anyone have a solution? Our system has 16 GB RAM and 12GB is reserved to SQL. Thanks,

Again. Brian Wleker told me last year it would be "fixed in the next update". I haven't tried SQL 2008 yet.

Hi, I am having issues similar to what other people are having. I am trying to export to excel and for a large set of data it just hangs. It hangs way before reaching excel limitation of 64K. Have any one found a solution to this problem. Will inreasing RAM or processing power of the server help? What if I upgrade to Reporting Services 2008, Will that work? Any help in this respect will be highly appreciated!. Thanks, Anthony Desa

Bumped to the same problem. My SSRS is 2008 Enterprise R2 edition which runs on W2K8 R2 Enterprise 64 bits server with 16GB RAM. The server is dedicated DB server and no other services are running on it. The report query is just a simple query (Select * from [Table] where month = @Month and year=@Year) which is already saved as storedproc. the query returns something over 30,000 rows (in 7 columns) from nearly 800,000 records in the table. in SQL Management Studio, it take less than a second to return the data. but when I put it into my SSRS report, it make problem. the report is just a tabular report with no calculation (just flat data) in the single page. (over 30 thousands rows in a same page :D, but it's the nature of the report. I can't change the format at this moment. ) In VS2008 or Report Builder 3.0, it takes about 3 mins to generate the report. but when I publish it to the report server and run from the browser, the report is never generated but make the browser also freeze and make me forced close the browser. Report Builder also crashes sometime with an error "There is not enough storage available to execute this command" can someone advise me what can i do to generate this report? Thanks in advance. Man may come and Man may go, but I go on forever