Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
Consider the following scenario:
You have a report that is created by using a version of SQL Server Reporting Services (SSRS) that is an earlier version than SQL Server 2008 R2 Reporting Services.
The report is large.
For example, the report has many pages.
You move the report to a SQL Server 2008 R2 Reporting Services server.
You view the report in Internet Explorer.
In this scenario, the report takes a long time to be displayed. Additionally, the CPU usage is high. However, the report-creation time is the same as the report-creation time for the same report before the report is migrated to SQL Server 2008 R2 Reporting Services.
Note The report-creation time is logged in the runtime logged data for the report.
If you disable the toolbar of the Report Viewer control by specifying the following parameter in the URL, the performance improves significantly:
This issue occurs because the HTML renderer of SSRS generates many <div> elements when you view the report in Internet Explorer.
Cumulative update information
The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2489376 Cumulative Update package 7 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
To work around this issue, use one of the following methods:
Optimize the pagination for the report when you design the report.
For more information about how to optimize the pagination for the report, visit the following MSDN website: