SAP_DEBUGGINGadvanced
Performance tracing, SQL and HANA analysis
An ABAP report is slow or data appears incorrect after query optimization. Learning outcome: Prove the bottleneck using traces before proposing code or index changes.
Overview
An ABAP report is slow or data appears incorrect after query optimization. Learning outcome: Prove the bottleneck using traces before proposing code or index changes.
Lessons in this topic
- Performance tracing, SQL and HANA analysis — Concepts and mental modelsLearn the root-cause mechanisms behind performance tracing, sql and hana analysis. Prove the bottleneck using traces before proposing code or index changes.
- Performance tracing, SQL and HANA analysis — Guided debugger and evidence walkthroughFollow six evidence-led steps to investigate performance tracing, sql and hana analysis. Prove the bottleneck using traces before proposing code or index changes.
- Performance tracing, SQL and HANA analysis — Root-cause case, remediation and assessmentPractice a realistic but fictional performance tracing, sql and hana analysis incident. Prove the bottleneck using traces before proposing code or index changes.
Interview questions covered
- How do you analyse a slow ABAP report?
- What is the N+1 problem in ABAP and how do you fix it?
Related topics
SAP_DEBUGGING
How experts find the real root cause
SAP_DEBUGGING
Classic and new ABAP Debugger
SAP_DEBUGGING
Advanced breakpoints, enhancement points and scripts
SAP_DEBUGGING
Update tasks, background jobs and dumps
SAP_DEBUGGING
RFC, BAPI, IDoc and output debugging
SAP_DEBUGGING
Eclipse ADT and ABAP OO debugging