I have a Reporting Services report running on a server. When I run a Reporting Services report (it doesn't seem to matter what report), I can see my processor shoot up to 50%. It stays at 50% long after the report has rendered. If I open another report in another window, my processor shoots to 90+ % even after the report is fully rendered. It doesn't seem to matter how simple the report is. If I close one of the reports, the processor goes back to 50%.
Keep in mind, this is the processor of the client machine and not the server.
What is going on? Why is a fully generated report continuing to use the processor? Is there some setting I need to adjust to have it not do this?
Server is Windows 2003 server using SQL 2005 and ASP.NET 2.0.
View Complete Post