Request level logging can be very useful in seeing what is actually happening in a live database, but the higher levels of logging (eg SQL, PLAN etc) do involve a fair degree of server load - especially with many hundred simultaneous users. Ideally one could just log a single connection but the way the docs read:
everything (ie for all connections / databases) is being collected (with the consequent server load) but the output is being filtered down to a single user.
Am I reading too much into the word "filtered" or is that the correct interpretation?
asked 10 Mar '15, 09:55
If my understanding of the docs is correct, you should be able to collect only RLL data for a specified connection via
So in my humble opinion that would mean the data collecion is already filtered, not the later RLL output. - Note, that's just another WAG for today:)