Re: Novice - Help with OLAP Design
- From: fimiani@xxxxxxxxxxxx
- Date: Mon, 30 Mar 2009 16:01:59 -0700 (PDT)
Craig,
Here I cheerry picked a few questions you had...did not answer all of
the questions...
Designing time dimensions ahead of time is probably the standard way
of doing it (though there are other ways, too, like putting something
in the ETL that looks at today's date and builds-out days or months
and/or whatever for that year, etc.), and since there are probably no
actual facts (barring budget and plan scenarios) associated with those
"future" time member, this probably does not cause any meaningful
query or cube processing costs.
Also, your comment about knowing what the reports need to look like
and then designing the cube from those needs might sound like a bad
plan to some, this is a common technique among consultants, and is a
very good guide -- with this exception: since the cube is also
intended to be ad hoc, as well as canned reports, and there are some
cases that go behond the current forseeable needs, the approach can
lose some benefits there. The more you get the end-users to think
about what they wold like to do with the mart, the better the result
should be...just asking them to layout on paper (or in a spreadsheet
is also good) what they want to be able to find out is a good way to
go. As part of that same question, there will be certain calcs/
metrics they want to know as well, whcih is apart from report layout
specs, obviously, but part of the same conversation.
Good luck...sounds like you're asking the right questions.
-exologic
.
- References:
- Novice - Help with OLAP Design
- From: Cralis
- Novice - Help with OLAP Design
- Prev by Date: calculated measure using properties - how to do roll ups
- Next by Date: Re: calculated measure using properties - how to do roll ups
- Previous by thread: Novice - Help with OLAP Design
- Next by thread: Named Set in Calc Script Doesn Not Return Members...Query-Scoped Set Does
- Index(es):
Relevant Pages
|
