Re: variable number of measures

#1

You will have to make the Attribute another dimension, and then have
AttributeValue to be a measure. If duration is not really dimensioned by
this Attribute, you may end up with 2 cubes, which can be joined in the
virtual cube. I.e

Fact Table for cube 1
------------
Dimension1_ID
Dimension2_ID
Duration

Fact Table for cube 2
------------
AttributeID
Dimension1_ID
Dimension2_ID
AttributeValue

Attribute Dimension Table
------------------------
AttributeID
AttributeName

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"John" <johnfj (AT) rogers (DOT) com> wrote

Quote:

I have a situation where for each item on the fact table there is a
variable
number of measures. For example say duration is a measure, but there are
also 0 to many "attributes" whose values are also measures. In the
database, I have this represented like so:

Fact Table
--------------
Record_ID
Dimension1_ID
Dimension2_ID
Duration

Fact-Attribute Table
---------------------------
RecordID
AttributeName
AttributeValue

I have read that to use analysis services to build the cube, I cannot have
measure on multiple tables like this and should consider deriving a view
to
act as the fact table? What options do I have here, especially if I do
not
know beforehand the name and number of "attributes" in my example above?

Thanks,
John

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: variable number of measures

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Re: variable number of measures - 08-18-2003 , 11:40 PM