Symptoms
Assume that you have applied one of the Cumulative Update (CU) from CU4 to CU8 for Microsoft SQL Server 2012 Analysis Services (SSAS 2012) SP1 that is in Tabular mode. When you use Multidimensional Expressions (MDX) with WHERE clause query or Data Analysis Expressions (DAX) query to select multiple dimension members, incorrect result is returned. It returns the sum of them instead of individual member result.
Note The issue also occurs in SQL Server 2012 Analysis Services (SSAS 2012) SP2 and SQL Server 2014 Analysis Services (SSAS 2014).
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 4 for SQL Server 2014 /en-us/help/2999197
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Cumulative Update 11 for SQL Server 2012 SP1 /en-us/help/2975396
About cumulative updates for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
- Latest cumulative update for SQL Server 2014
- Latest cumulative update for SQL Server 2012 SP2
- Latest cumulative update for SQL Server 2012 SP1
Workaround
To work around this issue, rearrange the relationship in group order based on the related column. For example, if TableA and TableB are both related to TableF through Column1, TableC is related to TableF through Column2, you may have to re-create (delete and create) the relationships manually based on the related column in the following order: the relationship between TableA and TableF, the relationship between TableB and TableF, the relationship between TableC and TableF. You have to reprocess the database in tabular after the workaround.
NOTE When you check the relationship, the GUI (through "Table" --"Manage Relationships" in SQL Server Data Tools) may show the different result from the actual deployed schema. Therefore it is best to script the database to XML for Analysis (XMLA) and review the relationship there.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.