August 19, 2015 at 12:18 pm
I am trying to track which CLRs are currently running as I see SPIDs that are executing managed code causing CPU contention.
I have tried using the sys.dm_exec_requests DMV where executing_managed_code = 1 and joining to sys.dm_clr_tasks and then joining those to assemblies etc. but all i get is a SPID with no indication of what managed code is currently being executing.
I have also tried using sys.dm_exec_connections and using the most_recent_sql_handle and passing that to sys.dm_exec_sql_text to see if I can identify the SQL that called it, but no luck unfortunately.
I used extended events to try to capture SP executions etc. no luck.
Can any help me track down which CLRs are being executed to identify the cause of CPU contention?
Thanks
Additional Info
This blog post by Glenn Berry doesn't particularly help https://sqlserverperformance.wordpress.com/2010/04/17/a-dmv-a-day-%E2%80%93-day-18/[/url]
August 20, 2015 at 12:29 pm
test
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply