I have a report running on our production Reporting Web server that is just spinning. When I run the procedure that the report runs directly on SQL Server using SSMS, it returns in a reasonable amt of time. I thought it might have something to do with the amt of rows that the report returns and that seemed to be it as I modified the stored procedure to return just the top 10 rows and it returned relatively quickly. However, our development reporting server runs a copy of the procedure except it pulls the same data from production via linked server and it returns the data quickly. So now I'm thinking that maybe production is running short of memory. How can I tell if lack of memory is a problem on reporting services? And if not, what else could be the bottleneckThanks much!
↧