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.

Symptoms

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 contains a large multi-select drop-down parameter list.

  • 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:

rc:Toolbar=falseIf you temporarily reduce the number of parameters in the multi-select parameter list, the performance improves.

Resolution

Cumulative update information



SQL Server 2008 R2 Service Pack 1


The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2544793 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1Note 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:

2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 R2


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, disable the toolbar of the Report Viewer control by specifying the rc:Toolbar=false parameter in the URL.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


We recommend that you control the number of items in a multi-select parameter list by using cascading parameters to improve the overall user experience. For more information about some similar performance issues, click the following article titles to view the articles in the Microsoft Knowledge Base:

FIX: It takes a long time to open a SQL Server 2008 R2 Reporting Services report that contains many parameter values in Internet Explorer

A Beta version of an update rollup package is available for the .NET Framework 4

FIX: Performance decreases after you migrate a large report to SQL Server 2008 R2 Reporting ServicesFor more information about report server runtime log, visit the following Microsoft websites:

General information about report server runtime log

General information about querying the runtime log data

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×