Different results for MDX queries when using Attribute Hierarchies


we receive different results follow 2 mdx expressions.  difference second parameter in clause uses separate dimension called asset class in first query,  whereas in first uses attribute hierarchy dimension  on asset dimension.

 

the first provides expected results top 10 equity assets, whereas second returns 3 equity assets belong top 10 assets overall.

 

can explain this?  using cross join in topcount function works, unfortunately proclarity using not deal properly.

 

 query 1

 

select non empty { [measures].[value base] } on columns ,

 

non empty { topcount( { [asset].[asset].[all].children }, 10, ( [measures].[value base] ) ) } on rows 

 

from [miqb daily]

 

where ( [period].[month].&[2005-11-01t00:00:00], [asset class].[asset class category].&[equity])

 

 

 query 2

 

select non empty { [measures].[value base] } on columns ,

 

non empty { topcount( { [asset].[asset].[all].children }, 10, ( [measures].[value base] ) ) } on rows 

 

from [miqb daily]

 

where ( [period].[year month hierarchy].[month].&[2005-11-01t00:00:00], [asset].[asset class hierarchy].[asset class category].&[equity )

this known bug microsoft fixing (see http://forums.microsoft.com/msdn/showpost.aspx?postid=549706&siteid=1). should end of august. major fix backported sp1 (as required fixes sp2 branch).


SQL Server  >  SQL Server Analysis Services



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........