-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Column 'X' does not belong to underlying table 'events' #14
Comments
Hi Tom, thanks for reporting the issue. |
I've found the problem with the I can share the session and json, but the XE data will be hard to reproduce. It monitors Linked server calls through a Service Broker activation. |
This is the XE session (I'm planning to blog about it after SQLbits ;) )
And this is the json
And the table definition
I've tried to use the |
Thanks! I'll have a look as soon as possible (might take a while...) |
Huh, sorry, which version? |
According to GitHub - Latest 1.4.5 (downloaded yesterday). |
Ah, gotcha. So it didn't work in 1.4.3 but it works in 1.4.5. |
Sorry, it was probably confusing. Problem 1 - I didn't realize filtering requires the column to also be on the output (that was mistake on my part) I thought maybe doing filter on the is_system and splitting it into two responses could get around that. But the events table check is probably before the filter check. It still fails. The only workaround I can think of is to split my Extended event into two session (one for system and one without) |
Ok, I had another wrong assumption. Updating my filter to I think the issue can be closed as there is a workaround by using several responses with the relevant filter. |
Awesome, thanks for the feedback. |
Update: Sadly it's not fixed for me. For some events, the sql_text is just not collected and I can't see any pattern explaining why. You said the data type is based on the underlying field. |
I have a peculiar problem. I'm tracking an event and collecting the
sql_text
global field/action.But when the event has column
is_system = true
then sql_text is not collected at all (the schema shape has changed)Service Broker activation is considered a system process even though it's arguably a user process.
I propose that the XESmartTarget return a NULL when the column is not found instead of the error. The SSMS XE viewer acts the same.
I've also tried to split the collection into two responses - one where
is_system = 'False'
collects the sql_text and the other one which doesn't. My filter snippet looks like this:"Filter": "query_hash_signed <> 0 OR is_system = 'True'"
Then I've got an error:
This is weird because the column is definitely there.
The column is recognized when I set up a different XE with a different JSON.
The text was updated successfully, but these errors were encountered: