SAP NetWeaver AS ABAP Administration

Performance Analysis & Trace Tools

26 flashcards · answers and review in the app

What four trace types does ST05 offer, and how can they be combined?
In current SAP systems, which transaction combines the SQL trace and ABAP runtime trace for analyzing one transaction?
Which developer traces does each SAP process write, and where?
What does the developer trace level rdisp/TRACE control, and why keep it low on a live system?
What is exclusive debugging mode, and why is nonexclusive mode blocked in production?
What are the ABAP debugger flow-control keys, and which system fields are shown?
Why should runtime analysis and performance trace be avoided in production, and how do you limit their impact if needed?
What is the difference between session and external breakpoints in the ABAP Editor?
Where do you check buffer quality, SAP memory usage, and table call statistics?
What does the Single Activity Trace (SAT) add over SE30?
What does the SAP system trace (ST01) log, and why is it unsuitable for live operation?
What can the performance trace (ST05) collect, and how is it used?
Where is database activity and table/index resource usage analyzed?
What happens to developer traces on restart, and how can you view them?
Which transactions provide workload monitoring statistics?
Where do runtime analysis results go, and how is that storage capped?
How do you inspect a single SQL statement's execution plan in ST05?
In a summarized SQL trace, what does a high Identical % signal, and what is a typical indexed-read time?
Which collectors gather performance data, and where do they write?
In which developer transactions can you use the new ABAP Editor, and how?
Why is the SQL trace the most-used ST05 type?
What does the new debugger need, and how do you terminate it?
When is the ABAP Runtime Analysis (SE30) the recommended entry point, and what does it measure?
Which transactions monitor operating-system resources?
Where do ST05 trace files live, and which parameters govern their name, size, and count?
Why does the new ABAP Debugger survive roll-area changes that would kill the classic debugger?