Here we have a something called as a SET A and SET B. Most of you must have had this math theory as part of your elementary math syllabus. At this point of time, we should not bother much about that aspect of math, but you must observe here is that that ‘something’ which calls itself as SET A resides within something which takes pride in calling itself as SET B. Voila!! We now have achieved a brilliant relationship between SET A and SET B, which now can be defined as SET A is the ‘subset’ of SET B.
Let us now take a step further. Now on similar lines, we can also achieve a theory which states that every set is a subset of itself. From the diagram above, SET B is a subset of itself. That’s enough for the math revision folks, before the site administrators yell at me, I will now begin the technical aspect.
The striking similarity here is the phenomena called as ‘perspective’ is derived from this very basic math feature which we have revised. I will now quote the biblical definition of perspective provided by the Microsoft itself:
A perspective is a subset of a cube created for a particular application or group of users. The cube itself is the default perspective. A perspective is exposed to a client as a cube. When a user views a perspective, it appears like another cube. Any changes made to cube data through writeback in the perspective are to the original cube.
For the sake of simplicity, I will not touch the last statement which tries to introduce a not so related aspect of dimension writeback as far as scope of this article is concerned.
The sole objective of the perspective is to enable ‘easy cube navigation’ and definitely not security. The perspectives can be used to hide entities like measures, measure groups, dimension, actions, KPI’s and calculated members thereby provide a customized ‘view’ of a larger picture.
Suppose you have a cube with say (one for human resources, one for finance, one for sales etc..) measure groups and many associated dimensions. The objective is not to make the entire cube space available to the designated user, but allow only a subset to which the user belongs. By this, the user from human resource can view underlying cube data from its designated perspective.
Hope this helps!!
t: @raunakjhawar e: firstname.lastname@example.org
i have the requerement to bring as default a subset of the cube. For Example, i should hide sales from the year 2000. Is this something for perspectives ? Or are perspectives used to hide some kpis or some dimension ?
Leave a comment