Performance with Calculation View V/S join on Webi queries

[Former Member]

Hello Team,

Good day!

I am working on a requirement wherein the reporting is to be done in Webi on the analytical view developed in SAP HANA studio.

This Analytical View has 4 lines of data with respect to one key field.For reporting, data is to be mereged into one single row based on the key field.

To cater to the above requirement, there are two approaches desgined

Solution 1 :

1. Analytical view to be created on the required table
2. Create projections on this analytical view ( In this particular scenario there are 4 projections required,where each of  these projections have different set of fields based on single key field.These projections are made on different filter criterias)
3. Join these projection into a single Calculation view based on the key field
4. Create universe using this calculation view
5. Create a Webi report directly on the caluclation view

Solution 2:

1. Analytical view to be created on the required table
2. Instead of creating projections, directly create a universe on the analytical view
3. Create 4 different queires ( by adding the respective filters as added in projection ) and merge them in the Webi report on the common key field.

Kindly help me analyse the performance watchpoints in the above two solutions proposed.

Regards,

Priya

[Former Member · Accepted solution]

Hi Priya,

From a performance point of view solution 1 will be desired as you are leaving the processing to happen within the faster Calculation engine of HANA thereby exploiting the much quicker HANA processing capabilities. With solution 2, you are adding an additional overhead of processing within Universe and Webi.

As a general priniciple/best practice, do as many as calculations/derivations as possible within HANA and aim to keep processing within the Universe/IDT/Webi/other reporting tools simple and straight forward.

Thanks,

Anooj

[rama_shankar3]

Priya:

Solution 1 - since the main purpose of projection option within studio is for the discussed scenarios and to take advantage of SAP HANA hardware (MPP, etc..)

Regards,

Rama

[Former Member]

Hello Priya

  In continuation to the above said by Anooj and Murali, if you use SQL Script calculation views instead of Graphical, it would add for your performance, as there are multiple joins involved in the scenario, and there CE functions for projections and JOIN , you can use SQL script ,CE functions to produce more performnce oriented results.

Please let us know your feedback.

Thanks

Santosh

[hai_murali_here]

Hi Priya,

As Anooj pointed out,its recommended to go with Solution 1 as you do processing in DB Layer itself,instead of bringning them into App Layer.

Rgds,

Murali