Hi, I'm in a Cognos planning implementation project as key user. We are working on application for cost center planning which includes the following dimesions and their sizes:
time - 12 month X 5 years
version - 5 versions
cost center - 355 cost centers
cost elements - 92 elements
They make the current designed cube really huge, like more than 10m cells. And I'm really concerned whether this has any sustainability.
Could some one share your experience on this?
this is one of cubes in the app so the elist slice must be more than that. per cognos it is certainly not the ideal cube/app size i.e. more than 500K/elist (cognos recommendation). but i have seen/worked on apps with more than 20 mln cells/elist.
since you are one of key users you would be more concern about the contributor web client functionality.
-due to this cube size you wont be able to open multi elist view. normally users like this feature not only for data entry ease but also for get data. it is very frustrating for users if they dont get this functionality. for one of clients, i had to reduce the model size so that users can use multi elist view feature.
- even if you are able to open multi elist view, it could create problems in saving data due to memory constraint as multi elist view requires more memory on client machines.
- it could be little slower in opening elist node.
if there are complex calcs/links involved than it makes things worse.
if you have concern about any specific functionality/feature due to large cube size than let me know.