I am creating a simple SAS 2005 Cube. One of the things I want is a time
dimension with the hierarchy Year -> Quarter -> Month -> Date.

This time dimension shuold relate to a datetime field in my fact table.

In Analysis Services 2000, I would just drag my datetime field from my fact
table to the Dimensions Folder and it would ask me the levels I wanted and
then I was done.

I am sure this is something simple, but I cannot find anywhere how to do
this... I am still new at SAS2005, and this is the last thing keeping me
from publishing my 1st Cube.

First, there is no customized member key/name column as in AS 2000. So every
customized member key/name column is reflected in data source view, which is
in turn used for attribute hierarchies such as Year, Quarter, Month, and so
on.

Next, you can make user hierarchy using attribute hierarchies. Below is
about "How to: Add or Delete a User-Defined Hierarchy "

http://msdn2.microsoft.com/en-us/library/ms175442.aspx


Ohjoo


"oe" <nosapm (AT) nosamp (DOT) com> wrote

I guess I am not getting that...

I don't need a customized member key/name is AS 2000. It creates the
dimension with the levels I choose (Year, Quarter, Month, Date) just from me
dragggin the column from the fact table into the Dimension Folder in the
AS2000 Cube Editor.

So in SAS2005, I create a new dimension and point it at the datetime field
in my fact table. I looked at user definied heirarchy you mention, but that
does not let me add anything. If I process the cube and browse it, I get
each individual date as a dimension, but no ability to roll that up to
month, quarter, and year.



"Ohjoo Kwon" <ojkwon (AT) olap (DOT) co.kr> wrote

In AS 2000, the built-in wizard actually addes each level with customized
SQL expression at each member key/name column according to each level.

Unfortunately there is not the same built-in wizard in AS 2005. I guess it's
because we cannot use SQL expression directly at KeyColumns/NameColumn of
each attribute hierarchy. Instead we should define the expressions, for
example Named Calculation, in data source view first and just refer to it.

And... each attribute hierarchy should be defined before it is used for user
hierarchy.

Ohjoo


"oe" <nosapm (AT) nosamp (DOT) com> wrote

AS 2000 was hierarchical-based. AS2005 is attribute-based, so you'll
have to create your own hierarchies (user-defined hierarchies) as a
collection of related attributes. It's quite simple to make the [Year,
Quarter, Month, Date] hierarchy that you mentioned, but this time
there's no wizard to do it for you. You will have to design what
hierarchies you want and then build it.

oe wrote:

The right answer here though is to avoid using the fact table DateTime for
the Time dimension. A best practice is to use a fully-defined Date dimension
table which contains *all* dates in the range you care about and not just
the ones for which you have fact rows.

In fact, you can also use the Time dimension wizard to create such a
dimension table -- or use a server-generated Time dimension.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Ohjoo Kwon" <ojkwon (AT) olap (DOT) co.kr> wrote