How can time information in the SQL cache (M_SQL_PLAN_CACHE) be interpreted? It doesn't matter if a statement is executed 1 time with a duration ofġ000 seconds or if it is executed 1 million times with an averageĭuration of 1 ms, because in both cases the statement is responsible forĦ. Important in the area of performance analysis are SQL statements with a The statement ID (column STATEMENT_ID) can't be used for that purposeĪs it is based on a connection ID and not on a SQL statement text.Īn expensive SQL statement is a database access that shows high values in areas like: M_EXPENSIVE_STATEMENTS or M_SERVICE_THREAD_SAMPLES. SAP HANA performance views like M_SQL_PLAN_CACHE, Is called statement hash and can be found in column STATEMENT_HASH of
Due to the fact that the text can be quite long and there can beĭifferent similar SQL texts it is useful to identify a SQL statementsīased on a hash value that is derived from the SQL text. Quite obviously a specific SQL statement can be identified by its SQL More information about an optimal SAP HANA performance configurationĪnd useful prerequisites for performance and SQL statement optimization. Longest running current SQL statement (s)Įxp. SQL using in average > 1 thread (last day) SQL using in average > 1 thread (last hour) SQL using in average > 1 connection (last day) SQL: "HANA_Configuration_MiniChecks" (SAP Notes 1969700, 1999993) returns a potentially critical issue (C = 'X') for one of the following individual checks: The following SAP HANA alerts indicate problems in the SQL area: If you want to optimize ABAP coding for SAP HANA, you can refer to the blog Performance Guidelines for ABAP Development on SAP HANA. The SAP HANA Troubleshooting and Performance Analysis Guide contains detailed information about tuning SQL statements. Why are there significant differences between SQL statements on ABAP and SAP HANA side?Ģ0. How can the performance of INSERTs and data loads be tuned?ġ9. Is it possible to capture bind values of prepared SQL statements?ġ8. Can sorting be supported by an appropriate index?ġ7. Are all database operations recorded in the SQL cache (M_SQL_PLAN_CACHE)?ġ6. Is it required to create optimizer statistics in order to support optimal execution plans?ġ5. Are there standard recommendations for specific SQL statements available?ġ4. Which advanced features exist for tuning SQL statements?ġ3. Are secondary indexes required to provide an optimal performance?ġ2. What are typical approaches to tune expensive SQL statements?ġ1. Which options exist to understand the execution of a SQL statement in detail?ġ0. How can I determine and interpret basic performance information for a particular SQL statement?ĩ. How can I determine the most critical SQL statements?Ĩ. How can time information in the SQL cache (M_SQL_PLAN_CACHE) be interpreted?ħ. How can I identify a specific SQL statement?Ħ. Which prerequisites are helpful for SQL statement tuning?Ĥ. Which indications exist for critical SQL statements?ģ. Where do I find information about SQL statement tuning provided by SAP?Ģ.