Hi, I’ve converted my RS project from 2005 to 2008 R2 version. I’ using Report services with SharePoint 2010 integrated mode. The report has some parameters and a stored procedure as a data source. One of the parameters contains about 2000 values In VS preview the report works quickly, but when I deploy report on SharePoint it works very slowly and Internet Explorer 8 uses high CPU. Why? select @@version -------------------------------------- Microsoft SQL Server 2008 R2 (RTM) - 10.50.1734.0 (X64)

Hi eldar, First of all, go to the report server database and query the report's TimeDataRetrieval, TimeProcessing and TimeRendering from the report server database's ExecutionLog2 view. TimeDataRetrieval The number of milliseconds spent interacting with data sources and data extensions for all data sets in the main report and all of its subreports. This value includes: - Time spent opening connections to the data source - Time spent reading data rows from the data extension Note: If a report has multiple data sources/data sets that can be executed in parallel, TimeDataRetrieval contains the duration of the longest DataSet, not the sum of all DataSets durations. If DataSets are executed sequentially, TimeDataRetrieval contains the sum of all DataSet durations. TimeProcessing The number of milliseconds spent in the processing engine for the request. This value includes: - Report processing bootstrap time - Tablix processing time (e.g. grouping, sorting, filtering, aggregations, subreport processing), but excludes on-demand expression evaluations (e.g. TextBox.Value, Style.*) - ProcessingScalabilityTime (see AdditionalInfo column) TimeRendering The number of milliseconds spent after the Rendering Object Model is exposed to the rendering extension. This value includes: - Time spent in renderer - Time spent in pagination modules - Time spent in on-demand expression evaluations (e.g. TextBox.Value, Style.*). This is different from prior releases, where TimeProcessing included all expression evaluation. - PaginationScalabilityTime (see AdditionalInfo column) - RenderingScalabilityTime (see AdditionalInfo column) see http://blogs.msdn.com/b/robertbruckner/archive/2009/01/05/executionlog2-view.aspx for more details on anylzing one report processing. Then, we can determine if the issue is for data retrievel, processing or rendering. thanks, Jerry

Hi Jerry, The result of the test is listed below: 1. After choosing parameter's values I clicked apply at 2:11:20 PM 2. At 2:14:54 PM I saw report's data on the screen select TimeDataRetrieval*0.001 TimeDataRetrieval, TimeProcessing*0.001 TimeProcessing, TimeRendering*0.001 TimeRendering, TimeStart, TimeEnd from dbo.ExecutionLog2 TimeDataRetrieval TimeProcessing TimeRendering TimeStart TimeEnd 10.245 0.135 0.037 2010-10-21 2:13:31 PM 2010-10-21 2:13:42 PM And this is result of the test after removing parameters with 2000 values about 1. After choosing parameter's values I clicked apply at 2:18:25 PM 2. At 2:18:30 PM I saw report's data on the screen TimeDataRetrieval TimeProcessing TimeRendering TimeStart TimeEnd 2.103 0.129 0.043 2010-10-21 2:18:25 PM 2010-10-21 2:18:28 PM