Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) update release.
Symptoms
Consider the following scenario:
-
You create a Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) report.
-
You specify the FixedColumnHeaders or FixedRowHeaders property for a tablix of the report to True.
Note The FixedColumnHeaders and FixedRowHeaders properties are used to indicate whether the column or row headers are displayed on the page when the user scrolls part of the tablix off the page. -
You set the LayoutDirection property to RTL for the tablix.
-
You deploy the report and render it in HTML format.
-
You scroll part of the tablix off the page horizontally or vertically.
In this scenario, no row or column headers are displayed.
Resolution
Cumulative update information
Cumulative update package 3 for SQL Server 2008 R2 SP1
The fix for this issue was first released in cumulative update package 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2591748 Cumulative update package 3 for SQL Server 2008 R2 SP1Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 SP1 update release. We recommend that you consider applying the most recent update 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 SP1 was released
More Information
For more information about the LayoutDirection, FixedColumnHeaders, and FixedRowHeaders tablix properties, visit the following MSDN website:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
