We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A checked box would just need to add "TRACK_CAUSALITY=ON" at the end of the Create Event Session. https://docs.microsoft.com/en-us/sql/t-sql/statements/create-event-session-transact-sql?view=sql-server-ver16#track_causality---on--off-
Adds 2 columns to every event, named attach_activity_id.guid and attach_activity_id.seq. Helps in filtering result set.
Need to confirm what versions this started working in and don't turn it on if this... FIX: TRACK_CAUSALITY causes access violations for batch completed event or RPC completed event in SQL Server 2014 (microsoft.com)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A checked box would just need to add "TRACK_CAUSALITY=ON" at the end of the Create Event Session.
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-event-session-transact-sql?view=sql-server-ver16#track_causality---on--off-
Adds 2 columns to every event, named attach_activity_id.guid and attach_activity_id.seq. Helps in filtering result set.
Need to confirm what versions this started working in and don't turn it on if this...
FIX: TRACK_CAUSALITY causes access violations for batch completed event or RPC completed event in SQL Server 2014 (microsoft.com)
The text was updated successfully, but these errors were encountered: