on 2015 Apr 29 5:29 AM
Dear Experts,
I have a scenario where we used 2 analytic views A,B and on top of them there are 2 calculation views C(on top of A) and D(on top of B).
Calculation views are created just for aggregation purpose.
In re-designing above scenario, Will it be good to use only calculation view including all the things from Analytic view and use aggregation as in previous calculation view?
Is there any additional benefit in terms of performance or etc. if we build Calculation view on top of Analytic view just for Aggregation purpose?
Thank you for your help.
Regards,
Raghavendra.
Hi Raghavendra,
Analytic View itself is an OLAP objects which means it doesn't allow you to activate it with out having measures defined. When you have measures, based on the attributes you select the measure values will be aggregated with the aggregation type you choose in semantics.
If you have created calculation view just for aggregation purpose I would say you don't need calculation view.Look at the calculation view and identify what thing has been applied ans see if you can achieve everything in Analytic view, then go for just analytic view.
Coming to which one performs better, it again depends.Based on my experience I would say Analytic View, however you can create both and see which one is performing better.
Regards,
Venkat N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
67 | |
8 | |
8 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.