richard bond®!ž‹)jiè²–¦

Hello,

I have a parent child dimension and a facts table that contains the data for
each member of this dimension (for every measure).I therefore don't need any
aggregation or rolling up to occur?

I am getting confused between articles on "Aggregation" and "Rolling up".

I currently have an entire column of tildas (~) in my relational dimension
table.
I am currently using a unaryoperatorcolumn IN SSAS and pointing to this
column.

However I came across another article "Loading Aggregate Data in Yukon 2005"

http://www.sqlserver****ysisservices.com/OLAPPapers/Loading%20Aggregate%20Data%20in%20AS2005v2.htm

that has left me confused as the formula :
Calculate;
this = [Employee].[Employee].currentmember.datamember;

seems possibley relevant to my situation aswell (although I'm unclear where
to introduce this formula)

Is there anyone that can clarify , or point me in the correct direction?

regards,

Richard

ohjoo kwon

For example, assume dimension hierarchy and salary values below.

A - 300
|-A1 - 100
|-A2 - 200

However, As you know, non-leaf member cannot be populated from fact table
directly.
For this, AS generates system member and use it for data loading. It is a
datamember.
For example,

A
|- (A) - 300
|-A1 - 100
|-A2 - 200

Now what value do you expect for [A] member after aggregation? The value is
500 as following.

A - 500
|- (A) - 200
|-A1 - 100
|-A2 - 200

Here you can also reference the value of datamember of [A] by defining
Calculated Member as following.

(PC.CurrentMember.DataMember, Measures.Salary)


By the way, if you use unary operators, (~), the value is 200.

A (~) - 200
|- (A) - 200
|-A1(~) - 100
|-A2 (~) - 200

In AS 2000, you can expect the same behavior setting Custom Rollup Formula
of the PC dimension.
For example,

CalculationPassValue(PC.CurrentMember.DataMember, 0)

Also, you can expect the same value by defining Calculated Cells. For
example,

A - 500 (200)
|- (A) - 200
|-A1 - 100
|-A2 - 200

Calculation Subcube: PC.Members
Calcualtion Value: CalculationPassValue(PC.CurrentMember.DataMember, 0)

In AS 2005, you can expect the same effect as calculated cells using scope.
For example,

this = [PC].[PC].currentmember.datamember;

Here, there is no scope expression, which means the entire cube.
Finally, "this" on left side means every cell within the cube.

Ohoo