1 person found this helpful
Thats fine the number of member in your applications, with this you should not think much as Account should always be dense and your case Product should be Sparse.
There are obvious reasons for the account structure to be dense -- most analytical applications run various formulas and such against different measures, so it only goes that in those cases, a dense dimension is better. There are execptions, of course (in some cases, you could say that the true 'measures' dimension isn't the account structure, but something else).
Changing a dimension from sparse to dense will increase the block size by the number of stored members in the time dimension times the current block size. The size change impact could be minor or significant depending on the existing block size and number of blocks.
This will also change the calculation order, which could affect calculated values.
Let us know if you have more questions.
Thanks KKT !
We have 2 Plan Types. In Plan 1 , Account is Dense, which are 800 members.
Here we discuss Plan 2, as we mentioned , only 30 members in Account.
My concern is, If we set Account dense in Plan 2, the block is too small, while the index will be too big.
I prefer to set Product dense in Plan 2, that could reduce block numbers and index, and made the block size between 80k ~100k. But I'm not so sure if it is the optimized way.
Thanks and regards
What you are do is
Make one dimension dense, load your data and check the block density - this will tell you which dimension is really dense.
Thanks Celvin , I think you are right.