Identifying “Expensive Statements” – Identifying performance killers
Came across interesting video tutorial from HANA Academy
This will be help full for Developers and Administrators to identify expensive (resource consuming, time consuming) SQL statements and optimize their query.
Jamie Wiseman will illustrate how to identify the most expensive statements that were executed on the system by activating the expensive statements trace. A statement is considered being expensive if its run time exceeds a particular threshold.
He explains two methods to set “expensive statement trace”
1. Using GUI wizards of Hana Studio
2. Using “Monitoring views” of SYS catalogue (where you can activate “Data preview” and perform some basic analytics)
You should be able to filter by User and Transaction ID and even can see the SQL statements which causes performance issues
Reference: SAP HANA Academy, http://www.saphana.com/docs/DOC-3517