You need to select a duration – 60 seconds is enough for me. You don’t want to be doing anything else with this user whilst you run this query. Give your trace a name – I called it slowquery.tpt, and optionally select your username as a restriction, if you’re sharing the system. Now select the little edit button, next to the Performance Trace. We can double click on our HANA system in the HANA systems view, which will bring up the HANA Overview. Admittedly, it’s a tough query, grouping 1.4bn transactions and counting over 2m distinct customers. This query takes 12 seconds, which is longer than I’d like. This is a fairly advanced topic, so beware!įirst, let’s pick a query which runs slowly. It is then possible to use HANA Studio to record performance traces, and analyze them with HDBAdmin. However, sometimes you need to get to a lower level of detail to understand exactly what is going on in the calculation engine. Most of the time, the Plan Visualizer is sufficiently powerful to understand what is going on inside of SAP HANA when you run a query.

Xming documentation