Ideally Account and Period are always dense.
But depending upon your business requirement and Dimesnions in your application you can change the property to either dense or sparse.
Have a look at Essbase DBAG to know more.
As per your example I will Tag A,B and C as Dense Only as it will lead to data blocks and page file calculations and performance impact as well.
To explain and you are aware - All of the dimensions are taken into consideration when creating a data value, both sparse and dense. You can't get around this and in Essbase you often see "No Product" or "No Customer" to allow the storage of a
data point that doesn't really make sense by Product or Customer.
the stored members of the dense dimensions are building the data block. A data block should not be too small and not be too large. Therefore, a large dimension will not likely be a candidate for becoming dense. Then I would prefer 3 small ones, even if they have a less data probability. When there are member formulas, or I can use member formulas instead of bringing them into a calc script, then this increases the possibility of this dimension becoming dense.
The given percentages of data probability are very high. I don't know how you got to these. I usually imagine a given data set with x thousand records. How many blocks would be created out of these, so the (remaining) sparse dimensions determine the data probability.
With other words, you cannot decide very well from the given examples. It requires a lot more.
I hope this helps.
Say if I have dimension with respective % of data probability. Which dimension wud u tag as dense and which as sparse.
A - 100%
B - 95%
C - 80%
Hi NJ. Can you define "% of data probability"?
For making dense / sparse decisions, the 'density' that matters is the ratio of members populated in the candidate dimension, for a given populated intersection of all the other dimensions. I would be very surprised (as Philip noted) if you really have a dimension that is 100% dense by this definition - unless it's an analytic dimension with only one stored member!