Comments on: I need to fix a very slow performing SQL Server Reporting Services report server.? http://www.indesicant.com/sql-server-hosting/i-need-to-fix-a-very-slow-performing-sql-server-reporting-services-report-server Powerful, secure, feature laden, high performance Windows and Linux web hosting Wed, 02 Jun 2010 03:18:59 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: SakuiWeb.com http://www.indesicant.com/sql-server-hosting/i-need-to-fix-a-very-slow-performing-sql-server-reporting-services-report-server/comment-page-1#comment-1920 SakuiWeb.com Fri, 12 Mar 2010 09:46:59 +0000 http://www.indesicant.com/sql-server-hosting/i-need-to-fix-a-very-slow-performing-sql-server-reporting-services-report-server#comment-1920 Use the sql query analysis tool, it will tell you where to index your tables and other such performance improovment techiniques.<br><b>References : </b><br> Use the sql query analysis tool, it will tell you where to index your tables and other such performance improovment techiniques.
References :

]]> By: Pimp Master G http://www.indesicant.com/sql-server-hosting/i-need-to-fix-a-very-slow-performing-sql-server-reporting-services-report-server/comment-page-1#comment-1919 Pimp Master G Fri, 12 Mar 2010 09:35:59 +0000 http://www.indesicant.com/sql-server-hosting/i-need-to-fix-a-very-slow-performing-sql-server-reporting-services-report-server#comment-1919 Have a look at the data that your report is selecting from your server. It could be that it's doing a massive join which performed OK with only 10 rows, but now it's dealing with 100 rows has grown exponentially. I'm assuming you're not running this report at a different time of day where the load on the server is different from the other reports running, and that there are no contention issues - have you checked locks? I'd say it must be a programming issue with the report -have you checked CPU usage on the box, is there enough ram to generate the report or is the server swapping? Have a look at the data though, and the number of rows returned - if possible separate the SQL from the report and run that via a console, does it still take as long?<br><b>References : </b><br> Have a look at the data that your report is selecting from your server.

It could be that it’s doing a massive join which performed OK with only 10 rows, but now it’s dealing with 100 rows has grown exponentially.

I’m assuming you’re not running this report at a different time of day where the load on the server is different from the other reports running, and that there are no contention issues – have you checked locks?

I’d say it must be a programming issue with the report -have you checked CPU usage on the box, is there enough ram to generate the report or is the server swapping? Have a look at the data though, and the number of rows returned – if possible separate the SQL from the report and run that via a console, does it still take as long?
References :

]]>