FIX: MDX query incorrectly returns a NULL value in SSAS 2008 R2 or in SSAS 2012 if a linked cube contains a many-to-many dimension and a distinct count measure group

Consider the following scenario:

• You create a source cube in Microsoft SQL Server Analysis Service 2008 R2 (SSAS 2008 R2) or in Microsoft SQL Server Analysis Service 2012 (SSAS 2012).
• You create a linked cube on a linked server. The linked cube is linked to the source cube.
• The linked server and linked cube meet the following conditions:
  • The linked server has a many-to-many dimension that contains no ALL member.
  • The dimension in the source cube is also a many-to-many dimension.
  • The linked cube contains a distinct count measure group.
  • You add a reference dimension to the measure group.
• You run a complex Multidimensional Expressions (MDX) query against the linked cube.

In this scenario, the MDX query incorrectly returns a NULL value.

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 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 2012 fix release. Microsoft recommends 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: You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 3 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: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:

SQL Server 2008 R2

The fix for this issue was first released in cumulative update package 9. 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: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:

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

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: