Question:
I have an issue....I told my team that Global keyfigures get calculated once for every cube and the local keyfigures get calculated for every query so performance increases if we use global keyfigures instead of local keyfigures and they are asking me for proof.I mean they want to know where it gets cached.Can anyone help me?
Answer:
An interesting question...
It seems to me that what you are storing in either case is just the formula for the calculated key figure, and therefore there would not be any performance difference between creating it as a global CKF and a local CKF.
The criteria we use to decide which to create is whether or not the CKF will be used in multiple queries. If so, we create it as a global CKF. Otherwise, we create it as a local CKF. When in doubt, we tend to use local CKFs.
The main reason for this is that if you create a global CKF and use it in a query, then transport the global CKF and query to production, the global CKF gets marked as "non-original" (just like the query). That means that if a user tries to create a query with the global CKF, they get an error due to restrictions on "modifying" non-original objects. In our case, we have instructed users who run into this situation to recreate the global CKF as a local CKF. You can imagine how much confusion that creates!
Hope this helps...
Bob