New Cube vs Scenario Type in Existing Cube
Hello, What are the factors one should consider while deciding between whether to create new cube vs using new scenario type in existing cube for different processes like Forecast/Budgeting etc.
W...
Forum Discussion
Hi Gaurav,
I agree with Teresa that Entity is the most common driving factor.
A few other reasons:
- Time profile - Monthly vs Weekly or multiple calendars are assigned at the cube level
- Security - you may want to consider splitting data & processes off to separate cubes depending on the security requirements. Ex. BUs don't want corporate to see their numbers until they are final.
- Cube as a dimension - Do you have a use case that will expand into multiple? Ex. You want to create a BudgetDrivers scenario but then what happens when you want to create a FcstM1Drivers, FcstM2Drivers, FcstM3Drivers, etc.? Using a separate cube as a dimension would allow you to reuse your existing Scenarios.
- Performance - not often, but in large-scale applications I've seen some resource-intensive processes take place in separate cubes where they can vary the cube settings (Cons algorithm, Business Rules, etc.). Teresa mentioned that resources are shared so there's no "true" performance gain, but the calc/cons times would be quick in one cube and longer in the other to potentially have less impact on some end users.
Hope it helps. I'm a big proponent of having purpose-driven cubes instead of separate cubes for every process where there's only 1 scenario type active in each.
Nick