Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MDX to manage a cube default

Status
Not open for further replies.

eo

MIS
Apr 3, 2003
809
I have a number of source systems in my cube data, the facts therefore can be sliced by a SourceSystem dimension. There is a requirement to exclude one of the source systems from the default.

Normally a default on the dimension would include one or more source systems [Policy].[SourceSystem].&[601], but I in effect have to do the opposite and not use this default MDX in an inclusive manner, but rather use it in an exclusive manner (I.e. Default to exclude SourceSystem 501). So I can only see two options:

1) Use an MDX script that somehow works in the opposite manner as the example [Policy].[SourceSystem].&[601] to exclude (not include) 501 as a default position, or

2) Use the less preferred option by speficying all the SourceSystems, except 501, which must be included in a default position, for example include 101, 201, 301, 401, and 601, so using some sort of MDX script to specify multiple defaults, not just [Policy].[SourceSystem].&[601]
- this is the less preferred option as it will require maintenance if new source systems come on board

Are either of these two MDX scripts possible??

EO
Hertfordshire, England
 
Could you Clarify what you mean by default? MDX can touch so many places that he term Default is very confusing.
 
There SSAS2005 is a DefaultMember property for each Dimension attribute. In there you have the ability to use MDX to define the default that will apply across the cube.

EO
Hertfordshire, England
 
You could try the Filter or IIF Functions to omit the values of the member you don't want included.
 
I am still at a loss as to how I would use it. For example the IIF (expression, true part, flase part) would require me to exclude 501 somehow. The DefaultMember property normally only requires a very simple MDX statement such as [Policy].[SourceSystem].&[601]. This would slioce the whole cube as a default start point with 601. Off-course if this property is left blank then the cube would default to the ALL member for that dimension. Is there not a way in MDX to say "Not 601" for example like in T-SQL where SourceSystem <> 601?

EO
Hertfordshire, England
 
Hi,

I have a problem in runing clustering algorithm for anomaly detection on cube. I wand filter many of my transactions in filter wizard by MDX operator for creating normal data for training phase. But i don't know how i can write a Query In "MDX builder"???? please write an example. where is the all examples about that??? is there any book or pdf about that????

Please Guid me
Naeimeh
 
In the absenswe of in depth knowledge of your problem, try the book "Fast track to MDX" by Mark Whitehorn which gives good guidance on MDX queries.



EO
Hertfordshire, England
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top