Have you looked into the SQL scripts in SAP Note 1969700?
Hi Michael,
I guess you mean this set of SQLs in SQL data collection, namely, ActiveStatements and ExpensiveStatements.
If I understood it right, ActiveStatements is a snapshot whereas ExpensiveStatements is only subset of statements.
What we need is to grab data about all SQLs in our predefined scope. Moreover, we need to log measures for a completed statement, how much CPU it took to fulfill a request etc.
We could fetch ActiveStatements data (or something similar) into our custom table(s) regularly (every sec or even every ms) but this would not guarantee we log the full picture.
Or maybe we could somehow change settings so all completed statements are logged in ExpensiveStatements. I understand it's a kind of crazy decision but it could give us the full log. Right?
Hi,
No, what you are referring to is the system views.The system views come standard with the system. The SQL scripts in the note were separately written and give far more detail and ease with option to modify in the MODIFY section. Please look at the note 1969700, its completely different. There is also a different note which explains each script and what it can do for you (searching you'll find this). I don't fully understand why you would like to analyse each SQL execution fully?. What is the business requirement for doing such a thing? Usually the situations I have seen just require analyse on a statement that is seeing some performance issues, rather than looking at every full execution?. There is a performance trace you can run, along with Plan Viz tracing? These should be sufficient for most cases I have seen.
Add comment