why we have Data Category to Cube or Dimension in Calculation view

[pavneet_rana]

Hi to a,,

Just want to know why we have Data Category to Cube or Dimension in Calculation view ?.

I tried to search the lot, but did not get correct explanation.

please can any one explain in simple example.

Regards

Pavneet Rana

[Former Member · Accepted solution]

Hello Rana,

If the data category is set to dimension,

• The output node does not offer any measures (or hierarchies), only attributes, which can be numerical data types
• The calculation view is not available for reporting.
• The calculation view is only consumable via SQL.
• The default node is projection.

on the other hand if the data category is set to a cube,

It is mandatory to specify at least one column as measure; otherwise, the view activation fails. Also, if the value is set to cube, an additional column called aggregation is available to specify the aggregation type for measures.

Regards,

Krishna.

[pavneet_rana · Accepted solution]

Thanks for reply,

one more small doubt,

what is use of check box with star join with data category CUBE.

1. What happen if with star join is selected

and

2. What happen if, we dont select star join.

Regards

Pavneet Rana

[former_member182302 · Accepted solution]

Have a look on the below blog:

Regards,

Krishna Tangudu

[pavneet_rana · Accepted solution]

Thanks for reply,

one more small doubt,

1. What happen if, we dont select star join.

Regards

Pavneet Rana

[former_member182302 · Accepted solution]

Nothing will happen, it will behave like normal calculation view.

Regards,

Krishna Tangudu

[Former Member · Accepted solution]

Hello Rana,

If you do not check the star join in sps07 when you select "CUBE" as your data category then the default node will be set to aggregation (for multidimensional reporting) instead of star join.

Regards,

Krishna.

[former_member184969]

Hi experts

Some more questions here :

- It's OK about the restrictions, but then...What are the benefits of using dimension calc views ? (especially as compared to attribute views).

- Do we ave any feed back on performances comparing the 2 of them ?

Regards

[lbreddemann]

The "benefit" is that the calc. views marked as dimension can be used as dimensions in calc. views with star joins. Also, dimension views don't come with default aggregation unlike fact-views.

Semantically this is the very same as attribute views and doesn't promise any performance improvement (or degration).

At this point this is more about being able to develop your whole information model as a set of calc. views and still having clear semantics defined for those.

- Lars

[justin_molenaur2]

Just so happens I was doing some research on this same topic - glad to have found you guys

Lars - in fact, you can have a calculation view defined as data category '' (blank) and you are still able to use it in a star join. So for me, I am trying to understand the difference between BLANK and DIMENSION. From what I see - no measures are possible with a DIMENSION, but you may have them available in BLANK, ie all are attributes. Otherwise, seems to be no difference - they both terminate with a Projection node.

Anything else pop in your mind?

Regards,

Justin

[lbreddemann]

Nope - I think you're pretty spot on with this description.

[former_member182302]

Adding to what already Krishna mentioned,

1) To make the calculation View which needs only joins and aggregations are not required.

2) These views ( Data category = Dimension ) in star join .

Regards,

Krishna Tangudu