« first day (4274 days earlier)      last day (609 days later) » 

5:46 AM
Helped I had an inside man
 
 
5 hours later…
10:53 AM
0
Q: A way to filter out parseonly statements from extended events?

MBuschiI'm currently using extended events to capture query statements executed on a production environment. But the actual session is capturing also the activity of 'query parsing' done by operators to evaluate if a query is well written. I would like to have an example of how to filter out SSMS activi...

@Zikato (and anyone else interested) I have reopened the above question.
 
11:47 AM
It's still not great
I wonder if Lucient would be interested in running a course about asking decent questions
Maybe they don't have anyone with those skills
In case anyone's wondering why I reopened it, it's because it no longer meets my bar for mod-closure, so I've effectively reversed my original action, that's all.
I can't see a way to do what he wants that doesn't involve checking to see if the previous batch issued by SSMS was SET PARSEONLY ON
TRACK_CAUSALITY would have to be on for that I think so you could check attach_activity_id_xfer was the same
But that would be filtering after the event. I think they want the event not to be logged in the first place.
 
1:02 PM
@PaulWhite anytime 😘
@PaulWhite I’ve often wished XE had a way to chain events so one would only fire if it met the filtering requirements of another but hey
 
Yes indeed
 
No one seems interested in my suggestions though
 
Perhaps you need more influence
Have you tied winning Red Gate awards?
 
Yeah we tied for 101 apparently 😃
 
So close
 
1:06 PM
Won’t be funny if you fix that typo
But let’s roll with it
 
Yeah I'll leave it be
On the XE thing, it's a bit weird they can't filter on environment settings like isolation level, SET options and so on
The existing connection event isn't very useful
Or comprehensive
 
Can you do that with Profiler
 
1:25 PM
As far as I know, the behaviour's the same
 
 
1 hour later…
2:33 PM
Well
that sucks
 
yeah, i think my use-case was only collecting queries after some condition with wait stats had been met
 
 
1 hour later…
4:13 PM
Brent's poll lol
 
4:39 PM
Why would anyone choose Profiler or XE there
@Zikato Strange reply from Erin? No way to know the GUID in advance? If only there were some other way to identify a stored procedure. Some kind of identifier, if you will.
But anyway, yeah, being able to collect related events would be most useful.
 
5:39 PM
@PaulWhite some people aren’t sorted for their e’s and wizz
 
 
4 hours later…
9:17 PM
That does explain it thanks
 

« first day (4274 days earlier)      last day (609 days later) »