![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
To speed up MDX query, often "Non Empty Behaviour" of the calculated measure is set to its measure key. Will this "non empty behaviour" setting have a performance gain if "IsEmpty()" function is used in the query and if "Non Empty" clause is not used in the query. OR is it necessary to have "Non Empty" clause to see the performance gain. I cant use "Non Empty" clause in my query because I need a subset() of first x non empty rows from the result. My query look like .. *********** Select subset(HIERARCHIZE(DISTINCT({FILTER( {{ [Product].[(All)].Members} * { [Channel Category].[Subcategory].Members} * { [Location].[State].Members}}, NOT ISEMPTY( [Measures].[Price]) ) })),0,10) on rows, HIERARCHIZE(DISTINCT({FILTER( {{ [Measures].[Price]}}, NOT ISEMPTY( [Measures].[Price]) ) })) on columns From [MySales] ************ |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Thanks Mosha for clearing the understanding.... But is it possibble to limit OR take the subset of the result returned by the query having "Non Empty" clause and CrossJoin() function.. so as to avoid empty data cells being considered by AS2K.. The work around about for this would help the community a lot ************** WITH SET [Myset] AS 'CROSSJOIN( { [Product].[(All)].Members} , Non Empty CrossJoin({ [Channel Category].[Subcategory].Members},{ [Location].[State].Members}))' Select NON EMPTY {[Myset]} on rows, {[Measures].[Order Count]} on columns From [Sales Aggregate] *************** |
![]() |
| Thread Tools | |
| Display Modes | |
| |