Select the product you need help with

FIX: A report displays incorrect results if you use a filtered shared dataset in a SQL Server 2008 R2 report

Article ID: 2515006 - View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

When you run a SQL Server 2008 R2 report under the following scenarios, you may encounter an issue.

Scenario 1

The report uses a shared dataset. You specify collation, case-sensitivity, and other options for the dataset.
You set a filter in the dataset.

In this scenario, the report displays incorrect results.

Scenario 2

The report uses a dataset. You specify collation, case-sensitivity, and other options for the dataset.
You set a filter in the dataset.
You create a parameter that is bound to the dataset.

In this scenario, the parameter lists incorrect values for selection when you run the report.

For example, assume that you create a shared dataset that contains the following data.

Collapse this tableExpand this table

Color	ID
Black	1
black	2

You set the case-sensitivity option for the dataset to false. Additionally, you set a filter that uses the following expression:

[Color] <> black

When you run a report that returns the shared dataset, the following data is displayed.

Collapse this tableExpand this table

Color	ID
Black	1

However, you expect the "black" row to also be displayed.

Back to the top | Give Feedback

This issue occurs because the collation, case-sensitivity, and other options are not considered when SQL Server processes the filter of a shared dataset or the parameter of a filtered dataset. If a different filter or parameter is used, this may cause an error.

Back to the top | Give Feedback

RESOLUTION

Service pack information for SQL Server 2008 R2

To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2527041

(http://support.microsoft.com/kb/2527041/ )

How to obtain the latest service pack for SQL Server 2008 R2

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in SQL Server 2008 R2 Service Pack 1 (SP1) for SQL Server 2008 R2.

Back to the top | Give Feedback