Hi BobP - BIM, As we can read from the Books Online, setting the WorkingSetMaximum value should limate the memory usage of SQL Server Reporting Services. Maybe the issue is caused by the location of the <WorkingSetMaximum> attribute in the RSreportserver.config file. At this time, I suggest that you modify the RSreportserver.config file as follows: <MemorySafetyMargin>80</MemorySafetyMargin> <MemoryThreshold>90</MemoryThreshold> <WorkingSetMaximum>4096000</WorkingSetMaximum> Please note that we need to resart the SSRS to make the above change effective. Hope this helps. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support

We have a reporting server that hosts our internal reporting and is also used with Report Builder 3. The specs of this server are: two 6 core processors and 32 gigs of memory. The box is running Windows 2003. I have read the article "Configuring Available Memory for Report Server Applications" and have set the WorkingSetMaximum. This is a copy from the config file: <WorkingSetMaximum>4096000</WorkingSetMaximum> <MemorySafetyMargin>80</MemorySafetyMargin> <MemoryThreshold>90</MemoryThreshold> However, the ReportingServicesService.exe continually consumes memory and does not release unless SSRS is stopped and restarted. Below is an image of the memory usage before and after the restart. ReportingServicesService released almost 20 gigs of memory. I have the RecycleTime set to 60 minutes, but that does not release the memory. Any ideas about what is causing this, and what I can do to remedy this? At night, this mild mannered reporting server becomes an ETL server and needs that memory. Thanks in advance! peace http://bobp1339.blogspot.com

It can happen for few reasons: 1. Number of report processed and inside the report if you use temp table to insert data, they hold memory by SQL 2008 Services. 2. Automated subscription to reports (if you have reports that run regular basis and send email) 3. Running any scheduled backup of Reporting Server 4. Number of user running reports at the same time 5. Any virus (unusual scenario)monir

But I have WorkingSetMaximum set to 4 gigs, which according to the Microsoft documentation, that "specifies a threshold after which no new memory allocations requests are granted to the report server allocations" http://bobp1339.blogspot.com

It will not allocate but it will be used by request. Allocation sometimes is just allocate memory for future use. For example, I allocate 2GB memory for my program. And this memory will be reserved/hold for me. No other program can use this. But if my program needs more memory, it will use more memory. I think you dont need to worry about adding this config. I am not sure though. But I never seen any report server in a stage "out of memory".monir

Please visit this link and read the details: http://msdn.microsoft.com/en-us/library/ms159206%28v=sql.105%29.aspx This specifically says: When the value for WorkingSetMaximum is reached, the report server does not accept new requests. Requests that are currently in progress are allowed to complete. New requests are accepted only when memory use falls below the value specified through WorkingSetMaximum." and then goes on about the MemoryThreshold and MemorySafetyMargin, which are percentages of WorkingSetMaximum. So it would seem that should limit how much memory the application domains use.http://bobp1339.blogspot.com

Please check SQL Server memory settings : Use SQL Management Studio and after connect to your SQL server, in Object Explorer, right-click a server and select Properties. Click the Memory node. Under Server Memory Options, enter the amount that you want for Minimum server memory and Maximum server memory. See if this helps to limit the memory usage by SSRS. monir

It does not affect SSRS. I already have that set to 2gig, and SQL Server respects that setting. Thankshttp://bobp1339.blogspot.com

Hi BobP - BIM, As we can read from the Books Online, setting the WorkingSetMaximum value should limate the memory usage of SQL Server Reporting Services. Maybe the issue is caused by the location of the <WorkingSetMaximum> attribute in the RSreportserver.config file. At this time, I suggest that you modify the RSreportserver.config file as follows: <MemorySafetyMargin>80</MemorySafetyMargin> <MemoryThreshold>90</MemoryThreshold> <WorkingSetMaximum>4096000</WorkingSetMaximum> Please note that we need to resart the SSRS to make the above change effective. Hope this helps. Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support

This did not fix the issue... It is still regularly consuming more than 4 gigs of memory. BobPhttp://bobp1339.blogspot.com