Re: Need help to build a dimension with duplicate members using a parent child

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Dave Wickert [MSFT] (dwickert_at_online.microsoft.com)
Date: 04/28/04 

Date: Tue, 27 Apr 2004 21:16:46 -0400

And make it a regular dimension. 

-- 
Dave Wickert [MS]
dwickert@online.microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave Wickert [MSFT]" <dwickert@online.microsoft.com> wrote in message
news:%23IlOMvLLEHA.3292@TK2MSFTNGP11.phx.gbl...
> Just change the "Allow Duplicate Names" to True.
> -- 
> Dave Wickert [MS]
> dwickert@online.microsoft.com
> Program Manager
> BI Practices Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "tdoyon" <thomas.doyon@cgi.com> wrote in message
> news:2754459b.0404270921.5f0b5cab@posting.google.com...
> > I need to build a dimension that would have duplicate member under
> > different parents.
> >
> > Something like:
> > A
> > -- B
> >     -- D
> >     -- E
> > -- C
> >     -- F
> > -- G
> >     -- D
> >
> > As you can see, the member D is under two different parents: B and G.
> >
> > The ideal way to build this dimension would involve using a table with
> > parent child relationship. The table would contain the following
> > records:
> >
> > Parent Child
> > A B
> > B D
> > B E
> > A C
> > C F
> > A G
> > G D
> >
> > This will not work with Analysis Service. You get the notorious error
> > "The dimension member key is not unique". Using the option "Names are
> > unique among: Not unique" doesn't help either.
> >
> > Any thought on this? My example above involves a dimension with only 3
> > levels, but my actual dimension actually has over 12+ levels. Please
> > consider it in your recommendations.
> >
> > I read another post that recommends changing the member key to a
> > combination of the parent key with the member key. Unfortunately, this
> > won't work in a multi-level dimension.
> >
> > For instance A->B can be changed easily to A->AB but how do you change
> > B->D? If you apply B->BD you will end up with a flat dimension (no
> > hierarchy) since the member B doesn't exist by itself anymore. The
> > correct conversion would be AB->ABD. Converting all the parent child
> > records to this new format seems very involved and complicated,
> > especially for a dimension with 12+ levels.
> >
> > Thanks in advance for any help or ideas
>
>

Relevant Pages

  • Re: large dimension with many member properties
    ... This is discussed in both the Analysis Services Perf and Operations Guides. ... Storage is dependent on the number of *independent* strings in a member ... if you had member property called "Gender" which contained one ... that the member property can be used as virtual dimension since the end-user ...
    (microsoft.public.sqlserver.olap)
  • Re: Question
    ... With over 50 million members, the Member Property/Virtual Dimension ... Microsoft SQL Server 2000 Analysis Services Operations Guide ... The number of member property settings in the dimension for all levels. ...
    (microsoft.public.sqlserver.olap)
  • Re: Aliasing Dimension Values
    ... so when the member is displayed, ... SQL BI Product Unit (Analysis Services) ... "rikesh" wrote in message ... > I have a dimension which is based on the Months of the Year. ...
    (microsoft.public.sqlserver.olap)
  • Re: Processing Cube works but shouldnt
    ... First of all, with the join to the dim, it won't ever see a row where ... the matching member doesn't exist. ... dimensions are processed independently in Analysis Services), ... that a member key for that dimension is missing and we return an error. ...
    (microsoft.public.sqlserver.olap)
  • Re: Truncate info for dimension members
    ... well as a base table) or 2) use TSQL substring on the member name field. ... Just run the dimension wizard and create the dimension. ... SQL BI Product Unit (Analysis Services) ...
    (microsoft.public.sqlserver.olap)