Skip to content
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

Error 468 Cannot resolve the collation conflict when running XE query inside MiscPssdiagInfo.sql #157

Closed
PiJoCoder opened this issue Apr 15, 2022 · 2 comments
Assignees
Labels
wave 1 - closed consider this issue for next wave of fixes

Comments

@PiJoCoder
Copy link
Collaborator

Do you want to request a feature or report a bug?
Bug.

What is the current behavior?

When databases are with different collation from that of Master, you may get Msg 468 when this query runs:

print '--XEvent Session Details--'
SELECT convert(nvarchar(128), sess.NAME) as 'session_name', convert(nvarchar(128), event_name) as event_name,
CASE
WHEN xemap.trace_event_id IN ( 23, 24, 40, 41,44, 45, 51, 52,54, 68, 96, 97,98, 113, 114, 122,146, 180 )
THEN Cast(1 AS BIT) ELSE Cast(0 AS BIT)
END AS expensive_event
FROM sys.dm_xe_sessions sess
INNER JOIN sys.dm_xe_session_events evt
ON sess.address = evt.event_session_address
INNER JOIN sys.trace_xe_event_map xemap
ON evt.event_name = xemap.xe_event_name

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem **

What is the expected behavior?

No error

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?

All supported versions

@PiJoCoder
Copy link
Collaborator Author

PiJoCoder commented Apr 15, 2022

Fixed by this commit:
fad1f92

@PiJoCoder
Copy link
Collaborator Author

already being fixed

@PiJoCoder PiJoCoder added actively worked Current issues being worked on right now and removed actively worked Current issues being worked on right now labels Apr 15, 2022
@PiJoCoder PiJoCoder added the wave 1 - closed consider this issue for next wave of fixes label Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wave 1 - closed consider this issue for next wave of fixes
Projects
None yet
Development

No branches or pull requests

2 participants