Monitoring Expensive SQL Statements – Missing Piece of the Puzzle for Performance Root Cause Analysis

Expensive SQL statements – impact on the system

Expensive SQL statements are long running statements, often seen as the main cause of performance problems. On top of causing long running programs, they also negatively influence other transactions. Even one expensive SQL statement can cause various problems such as high CPU utilization, high I/O loads, long blocking of SAP work processes and prolonged execution time of other SQL statements.

Expensive query monitoring helps you to define demanding processes happening on the system while experiencing performance bottlenecks. For these reasons, we always recommend customers to set up monitoring of their expensive SQL statements.

Monitoring – how to set it up right

The way to get the most out of your monitoring is to correlate SQL statements with other performance related factors. Hence, integrating the expensive SQL statement of your HANA in a system monitoring solution such as Datavard Insights can be extremely helpful. Such synchronization will enable you to tell what was happening on the system while you experienced certain problems. You will be able to see the effects the execution had on your system, move on quickly with root cause analysis and take precautions for avoiding similar issues in the future.

Top tip:When setting up expensive SQL statement monitoring on your HANA system, make sure to set meaningful thresholds for the statements’ size and execution time to choose which processes will be tracked. It is critical to choose a monitoring value bigger than 0 (which would cause monitoring all statements and impact the performance of your HANA system).

Datavard Insights with Integrated Expensive SQL Monitoring


Example of KPI correlation of Datavard Insights. The autocorrelation function finds the right KPIs to be on the lookout for. You can always customize the correlation by adding other critical KPIs to the range.

Leave a Reply

Your email address will not be published. Required fields are marked *