Skip to Content
Author's profile photo Yogesh Vijay

SAP HANA Calculation View Performance Tips

Hi All,


This blog is on some Performance tips in SAP HANA Calculation View.

Our basic aim to move to SAP HANA is performance and if performance is not so good then there is no meaning to a shift. Creating information views in HANA is not a big deal, however maintaining their performance is what needs time and understanding of various options SAP HANA provides.

First and foremost is SAP HANA’s engine, HANA provides three engines JOIN Engine, OLAP Engine and Calculation Engine. Apart from this there is one SAP HANA Query optimizer whose job is to actually handover data to separate engines depending on which engine performs better for that query.

When building Calculation Views, it is useful to keep in mind that which engine is predominantly used To give an example if the Calculation View is of type Dimension, processing goes to Join Engine, however if there is any calculated column then processing goes to Calculation Engine which sits on top of JOIN Engine. Similarly if the View is of type CUBE with Star Join then processing goes to OLAP Engine.

There are quite a lot of overlapping capabilities in engines and to identify which engine(s) is/are actually called at each step – we can use Explain Plan Tool (explained below)

Some points which can be taken care of while doing modelling

  • Try not to transfer large result sets between HANA DB and client applications (e.g. Analysis for Office)
  • Always try to do calculation after aggregation (Aggregation removes duplicate results or aggregate them before display)
  • One more thing is – try to avoid complex expressions in calculated column, either one can push down this into model itself
  • Doing JOINs on keys or indexed columns helps a lot in performance
  • Most important is Filter data as early as possible by using input parameters, Analytical Privileges, Aggregations, etc.
  • Also try to reduce data flow between views.

Apart from this one can use Execute In property in views (present in view’s property tab), if you set it to SQL Engine  then Calculation Engine try to generate SQL statements for each nodes and then create a big SQL query which then passes to SQL Query interface (which has standard SQL optimizer) which helps in optimizing SQL query – one is that it generates optimal JOIN sequence.

To have this – SQL Optimizer works and you need to make sure that you should not use any column store functions in filter or calculated columns (e.g. date(), time())

I will talk about SQL Script optimization in another blog.

Below are details of some tools which help in monitoring performance

  • Explain Plan tool : In this you can see which execution step uses which engine, through this you can avoid calling multiple engines by tweaking nodes in views, hence provides good performance.
  • Plan Visualize tool: I very much like this tool as it gives the complete picture of how the data is flowing in a view, how much rows of data is moving from one node to another.
  • Plan Execute tool : In this you can see execution time – which node is taking maximum time, how many tables were accessed, how many records, etc. I will recommend to see this when your are executing your views.
  • Timeline View: This gives time stamps for each SQL execution step. It is also a good view to see which step is taking maximum time.

Finally to see these tool you have to actually generate the SQL query of View, which you can generate by right click on the view and click on option Generate Select SQL. Now in the context menu you have options to select different tools (as shown below).


I hope this helps you when you are concerned about performance.

In case of any query regarding this feel free to add comments below, I will address them to best of my knowledge.



Yogesh Vijay

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo D D
      D D

      Hi Yogesh,


      Thanks for your blog.

      We are working on SAP BW 7.5 SP 11.

      We are starting to investigate on the HANA decision modelling to optimise our existing BW dataflow.

      I have a question, can we manage everything requirements only with the calculation view ?

      What would be the specific needs that we could not managed with calculation view and for which we would need attributes view or analytical view ?

      What are the things that we coud only do in attributes or analytical view that we could not do in calculation views ?

      Many Thanks


      Author's profile photo Vijay Dasari
      Vijay Dasari

      Hey DD,


      SAP suggests developers to develop Calculation views which accommodates Analytic View's and Attribute View's functionalities.

      You can use table functions (earlier scripted calculation views) to accommodate complex requirements.




      Author's profile photo Hari babu
      Hari babu

      Hi Yogesh ,

      Thank you for sharing .its very informative .you have mentioned that push calculated column to hana model itself .can you explain in details ? Assume I have to derive new columns based on different filter ? Assume I have to generate column based multiple conditions ?


      Author's profile photo Yogesh Vijay
      Yogesh Vijay
      Blog Post Author

      Hi Hari,


      By that statement, I mean that - if you are trying to calculate a few columns, then make sure to use Calculation view, however now the concept is changed a little bit. There is no different view,OLAP engine automatically decides which engine to start.

      You need to go through the SAP Help document for further investigation on this.


      Yogesh Vijay

      Author's profile photo santhosh kumar
      santhosh kumar

      Thanks Vijay, Understood to some extent.