This content has been marked as final. Show 3 replies
Why go through all of this? If you took those upper level loads in Accounts (fwiw, I almost always make dense dimensions fully dynamic) and stuck them into level zero buckets (No_Account, No_Whatever) then all of this would be moot and the data would be there, always no matter what you did with an aggregation.
It's a little awkward but really very easy to manage once done. I've never had a user that was confused by it.
Thanks Tim and Cameron. I think it is the SET AGGMISSG ON issue. And I agree with Cameron on the no_account design. It may take a while for me to convince my lead to change it. Also I am puzzled on why having 4 dense dimensions. Normally account and time dimension should be dense and others should be sparse. We are having some performance issue because of 4 dense dimensions make the database very big.