Skip to content
IT Canvass
SAP HANA · Lesson

Performance

Quick answer

Layer and simplify calculation/CDS views, push filters/aggregation down, and minimise data movement.

Key takeaways

  • HANA is fast because it is in-memory and columnar, so set-based scans and aggregations fly.
  • Use HANA’s tools, the SQL plan visualizer (Plan Viz) and Explain Plan to see how a query executes, plus the HANA cockpit for…
  • Row-by-row processing (loops) instead of set operations.
  • Watch out: Row loops instead of set-based logic.

What makes HANA fast, and how to keep it

HANA is fast because it is in-memory and columnar, so set-based scans and aggregations fly. You keep it fast by working with the grain: filter and aggregate in the database, avoid moving large data sets out, and prefer set-based SQL/CDS over procedural row loops.

Where performance is lost

  • Row-by-row processing (loops) instead of set operations.
  • Pulling large data to the app tier instead of pushing logic down.
  • Expensive joins / late aggregation in poorly-designed views.
  • Missing filters scanning more than needed.

Analysing performance

Use HANA’s tools, the SQL plan visualizer (Plan Viz) and Explain Plan to see how a query executes, plus the HANA cockpit for system-level monitoring. These show where time and memory go so you optimise the real bottleneck.

Modeling for performance

Layer and simplify calculation/CDS views, push filters/aggregation down, and minimise data movement. Because the engine is so fast, most remaining performance problems are design problems, solvable by better models and SQL.

Common pitfalls

  • Row loops instead of set-based logic.
  • Late/absent filtering and aggregation.
  • Not using Plan Viz/Explain to find the real issue.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of Performance?

    • A. At around 2 years of experience, interviews expect solid fundamentals plus real, hands-on work in your area…
    • B. SAP career growth means moving from doing (configuring/coding) to designing and leading, deepening expertise…
    • C. You keep it fast by working with the grain: filter and aggregate in the database, avoid moving large data…
    Show answer

    C. You keep it fast by working with the grain: filter and aggregate in the database, avoid moving large data…

    Covered in the “What makes HANA fast, and how to keep it” section of this lesson.

  2. Which of these also applies to Performance?

    • A. Use HANA’s tools, the SQL plan visualizer (Plan Viz) and Explain Plan to see how a query executes, plus the…
    • B. Learning screens, not the end-to-end process.
    • C. Confusing personalization with configuration.
    Show answer

    A. Use HANA’s tools, the SQL plan visualizer (Plan Viz) and Explain Plan to see how a query executes, plus the…

    Covered in the “Analysing performance” section of this lesson.

  3. Which part of the Learn SAP curriculum covers Performance?

    • A. SAP FI
    • B. SAP examples
    • C. SAP HANA
    Show answer

    C. SAP HANA

    This lesson sits in the SAP HANA section of the Learn SAP course.

Frequently asked questions

What does Performance mean in SAP HANA?

HANA performance is usually excellent by design, but realising it requires good modeling and SQL: pushing computation down, avoiding row-by-row processing, and writing efficient views. Poorly-written logic can be slow even on HANA.

What else matters for Performance in SAP HANA?

Layer and simplify calculation/CDS views, push filters/aggregation down, and minimise data movement.

What else should SAP HANA teams know about Performance?

HANA is fast because it is in-memory and columnar, so set-based scans and aggregations fly.

What tends to go wrong with Performance in SAP HANA?

Row loops instead of set-based logic. Late/absent filtering and aggregation. Not using Plan Viz/Explain to find the real issue.
CallWhatsAppEnquire