Hi Samuli,
Thanks for the hint, but hm, that is a quite general answer. I don't see my requirement reflected in the documentation. Just (processing-intensive in the meaning of) "long-running" statements I can analyse with an SQL trace (also done already). Anyhow, I need a specific approach to analyse which statements lead to big temp data and/or big results.
If this can be done specifically, could you point out how?!
Thanks in advance
Detlev