-
Notifications
You must be signed in to change notification settings - Fork 991
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
sp_BlitzWho returns multiple records for some session IDs #1089
Comments
Hello! I haven't come across this. Can you add some more details to this the next time it happens? We don't join to exec context id, and we're already summing these values I'm not calling you crazy, because we've run into multiple rows returned bugs in the past, just want to make sure i'm focusing on the right part of the code. If it's as simple as adding a Thanks! |
Nope - you're absolutely right. I'm definitely seeing multiple rows though and its only for sessions where there are multiple exec_context_ids but perhaps that was a red herring - I put 2 and 2 together based on the 5th June version being the first instance where this cropped up. I'll see if I can narrow it down further. |
Alright, this is probably going to need a TOP 1 in it, but incremental changes are probably smart. Can you test out the version here and let me know if anything is wonky? |
Yep that worked a treat! |
Awesome! I'm going to leave this open in case you spot anything else, or in case anyone else comes along with the same issue. It will likely go into the next FRK release. Thanks! |
Do you want to request a feature or report a bug?
Bug
Script: sp_BlitzWho
Version 5.4 - June 05, 2017 onwards
What is the current behavior?
Since this version, sp_BlitzWho returns multiple records for some session IDs due to the cross apply to tempdb allocations. This returns multiple rows when sessions have multiple exec_context_ids in sys.dm_db_task_space_usage.
What is the expected behavior?
A single row per session - I don't think the cross apply is working as expected.
SQL Version
I've seen this issue on Microsoft SQL Server 2008 R2 (SP3) - 10.50.6220.0 (X64)
The text was updated successfully, but these errors were encountered: