Re: Hierachies and Key Collections

Tech-Archive recommends: Speed Up your PC by fixing your registry

if the key of the month attribute is unique (ie 200301 to 200312) then there is no need for a composite key columns.
if the month key is only 1 to 12, then you need a composite key (Q1-01)
everything is ok until you are in an hierarchy.

now, if you need the month name only (jan to dec.) as a standalone attribute you have to create another attribute where the key is 1 to 12 and the label from jan to dec.
and hide the first month attribute which is not useful to use as a standalone hierarchy.

does this solve your issue?

<martinghale@xxxxxxxxx> wrote in message news:1190843559.937343.27550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

We are experiencing an issue and looking for advise and/or a solution
to this problem. It relates to the use of an attribute in an
attribute hierarchy as well as the same attribute in a user defined
hierarchy in which it is included in a key collection. Here are the
details:

Envrionment:
8 way 64 bit server, 65 GB memory
Windows Server 2003 Enterprise
SQL Server 2005 Analysis Services Enterprise with SP2

The issue is with out conformed Date dimension. We need to have each
attribute to be able to be used by itself (i.e. Year, Quarter, Month,
Day, etc...) as an attribute hierarchy to facilitate slicing and
dicing with Date periods on both the columns and rows of a cube
browser (e.g. Count by Quarter on Columns and Year on rows).

We also need to satisfy the user requirements of having several user
defined hierarchies (e.g. Year>Quarter>Month>Day, Year>Week,
Year>Month, etc...). Based on our reading, we need to define a Key
Collection on Quarter-Month for our scenario. Now because of this Key
Collection, the Month attribute can not be used by itself as an
attribute hierarchy.

Are we misunderstanding something? But if not what is the best
practice way around this issue? Currently we are using a duplicated
column but that seems 'hokey' to me.

Any advise/direction is greatly appreciated!

Thanks in advance.

Martin

.

Relevant Pages

  • RE: Problems with User Hierarchy and Member rollup
    ... out of 3 level hierarchy, I did not define a composite key. ... the Customer Geography user hierarchy, ... Therefore even though a member in level2 ...
    (microsoft.public.sqlserver.olap)
  • Hierachies and Key Collections
    ... We are experiencing an issue and looking for advise and/or a solution ... hierarchy in which it is included in a key collection. ... Windows Server 2003 Enterprise ... SQL Server 2005 Analysis Services Enterprise with SP2 ...
    (microsoft.public.sqlserver.olap)
  • Attribute hierarchy roll up
    ... repeated as if the hierarchy was built based on the composite key. ... When I browse the cube, the first level in the hierarchy shows 6 items ... dropped and recreated this dimension and hierarchy many times. ...
    (microsoft.public.sqlserver.olap)
  • Re: Need to forward request for a domain to another DNS server
    ... they would have to BE in a hierarchy ... >>> 192.168.0.3 not a root server ... >>> Active directory on both machines in the same time. ... >> DNS server set) there are two basic ways to get ...
    (microsoft.public.win2000.dns)
  • Re: Mulberry gone, now what?
    ... server decides the naming and hierarchy conventions, ... The idea here was that all clients of the server would be made to behave in the same way; and thus the server provider's helpdesk doesn't need to know how a particular client works. ...
    (comp.mail.imap)