I need to create very large reports 2000 pages+. Some reports could have a bunch of subreports that could total 50,000 pages. These reports need to be printed, and would be nice if they could be displayed on the report viewer. And yes I need reports this big, we print out pallets of pages. From the other messages, it seems like RS 2008 can do this, but do people have experience doing this? Any suggestions on the server memory/cpu? Is it possible to just export it to pdf? Would it be better just to do that? Can reporting services skip the viewer and just export to pdf? If I use RS, I'd also plan to use a silverlight viewer for it since our app is in silverlight. Do you see any problem with that?dan

I can tell you large reports are possible. We ran 2 procs with 24gb of ram do to the fact of alot of real time reporting. To help users and not use the viewer you could set them up as timed subscription directly to PDF or program a subscription on the fly to have it send as a PDF to the user at the time of request.Scott Schwarze MCT http://www.scottschwarze.com

Hi, This kind of large reports case. it is always recommended to have the report generation scheduled, the output format specified and copied into a shared location. Reason is, it takes good amount of processing. Hence, generating these reports on-demand would have a hit on response time. Also generally such bigger reports are meant for feed files to the downstream systems or kind of records that need to be submitted to legal. Refer to this link http://technet.microsoft.com/en-us/library/ms154040.aspx for more details. Let me know if you need more help. Regards,Phani Note: Please vote/mark the post as answered if it answers your question/helps to solve your problem.

Since you are using SQL 2008, dealing with large reports is pretty much possible. Dealing with large reports there is a very good article published in SQLCat, http://sqlcat.com/technicalnotes/archive/2008/07/09/scaling-up-reporting-services-2008-vs-reporting-services-2005-lessons-learned.aspx Also, its always suggested to create snapshot of the reports or schedule it at times when there is no heavy load on Reporting services, might be in midnights. Because based on the Report design, and the amount of data it returns Report execution might take time. Chaitanya

Since you are using SQL 2008, dealing with large reports is pretty much possible. Dealing with large reports there is a very good article published in SQLCat, http://sqlcat.com/technicalnotes/archive/2008/07/09/scaling-up-reporting-services-2008-vs-reporting-services-2005-lessons-learned.aspx Also, its always suggested to create snapshot of the reports or schedule it at times when there is no heavy load on Reporting services, might be in midnights. Because based on the Report design, and the amount of data it returns Report execution might take time. Chaitanya

Thanks for the responses. It seems like SSRS 2008 will work, and maybe write it out to PDF format. currently our customers are using a desktop program to create the reports, so the load is on their computer not the server. I'll be using silverlight, so I'm thinking maybe I should just feed the data with WCF to the silverlight client and use a 3rd party pdf writer to create a pdf. The wait time is not a problem, this will be an internal silverlight app and currently customers wait a couple hours for a report to generate (legacy system). The ideal situation for me would be to use telerik reports, it's like the report designer in VS 2010. I'm not sure if either can take such large documents though. My test server has less than 1gig of ram, so I guess I need a new test server. It would be easier than setting up report services on all our different customer's servers and have something else to monitor. Will SSRS 2008 handle large reports better than the report designer, or telerik reports (or maybe the same, just depending on the server's memory).dan

Hi Danparker276, This link supply some information about process large report, http://msdn.microsoft.com/en-us/library/ms159638.aspx There are some Configuration Recommendations, Rendering Recommendations and Deployment and Distribution Recommendations, you could click this link to get a reference. Thanks, Challen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Thanks for the links, that's helps a lot. One thing I'm still not sure about is will SSRS write the results to the disk/database or wil it keep it in memory? I really don't care about how long it takes to create the report, just as long as it creates it. So would it be possible to have a large report on a server that only has 4 gigs?dan

Hi danparker276, Reporting Services does not impose a maximum limit on the size of a rendered report. System memory determines the upper limit on size (by default, a report server uses all available configured memory when rendering a report), but you can specify configuration settings to set memory thresholds and memory management policies. For more information, see Configuring Available Memory for Report Server Applications. The only hard limit on report size is when rendering to Excel format. Worksheets cannot exceed 65536 rows or 256 columns. Other rendering formats do not have these limits so size is limited only by the amount of resources on your server. For more information about Excel file limits, see Exporting to Microsoft Excel (Report Builder 3.0 and SSRS). For more information about Report and Snapshot Size Limits, please see http://msdn.microsoft.com/en-us/library/ms156002(v=SQL.105).aspx Thanks, Challen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi danparker276, Reporting Services does not impose a maximum limit on the size of a rendered report. System memory determines the upper limit on size (by default, a report server uses all available configured memory when rendering a report), but you can specify configuration settings to set memory thresholds and memory management policies. For more information, see Configuring Available Memory for Report Server Applications. The only hard limit on report size is when rendering to Excel format. Worksheets cannot exceed 65536 rows or 256 columns. Other rendering formats do not have these limits so size is limited only by the amount of resources on your server. For more information about Excel file limits, see Exporting to Microsoft Excel (Report Builder 3.0 and SSRS). For more information about Report and Snapshot Size Limits, please see http://msdn.microsoft.com/en-us/library/ms156002(v=SQL.105).aspx Thanks, Challen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi danparker276, Reporting Services does not impose a maximum limit on the size of a rendered report. System memory determines the upper limit on size (by default, a report server uses all available configured memory when rendering a report), but you can specify configuration settings to set memory thresholds and memory management policies. For more information, see Configuring Available Memory for Report Server Applications. The only hard limit on report size is when rendering to Excel format. Worksheets cannot exceed 65536 rows or 256 columns. Other rendering formats do not have these limits so size is limited only by the amount of resources on your server. For more information about Excel file limits, see Exporting to Microsoft Excel (Report Builder 3.0 and SSRS). For more information about Report and Snapshot Size Limits, please see http://msdn.microsoft.com/en-us/library/ms156002(v=SQL.105).aspx Thanks, Challen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help. Yeah I saw that, it seems to keep the whole report in memory, I was hoping maybe there would be a setting to hold the results in a temporary database table and read the results one page at a time. I'll probably be ok as long as I have a large server. I'm comparing SSRS vs telerik reports and they both seem to hold the report in memory, so I'm guessing both would have the same size limit (unless there are some rendering problems with large reports for telerik)dan