You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of the script
SELECT @Version = '8.11', @VersionDate = '20221013';
What is the current behavior?
Currently sp_BlitzWho will show tempdb allocations only for user objects such as temp tables etc but does not take into account internal objects such as workfiles and worktables.
If the current behavior is a bug, please provide the steps to reproduce.
Run a query that uses a worktable and/or workfile which takes at least a few seconds to run to allow you time to run sp_BlitzWho with expertmode = 1 in another query window and observe the tempdb allocations column..
Steps:
Confirm that this query uses a worktable and/or a workfile (it used both for me).
SET STATISTICS IO ON;
SELECT *
FROM [dbo].[BlitzFirst_FileStats_Deltas]
just to make that query take longer on my system I did a cross apply like this in query window 1:
SELECT *
FROM [dbo].[BlitzFirst_FileStats_Deltas]
CROSS APPLY (SELECT TOP 3 [number] FROM [master].[dbo].[spt_values]) x /* do this just to make the query take longer */
In Query window 2:
EXEC sp_BlitzWho @ExpertMode = 1;
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
Tested with SQL2012 and SQL2016
The text was updated successfully, but these errors were encountered:
@Adedba I haven't heard back from you, so I'll go ahead and close this for now, but if you decide you want to work on it, you can leave a comment here when you're ready to do a pull request, and I can reopen it.
Version of the script
SELECT @Version = '8.11', @VersionDate = '20221013';
What is the current behavior?
Currently sp_BlitzWho will show tempdb allocations only for user objects such as temp tables etc but does not take into account internal objects such as workfiles and worktables.
If the current behavior is a bug, please provide the steps to reproduce.
Run a query that uses a worktable and/or workfile which takes at least a few seconds to run to allow you time to run sp_BlitzWho with expertmode = 1 in another query window and observe the tempdb allocations column..
Steps:
Confirm that this query uses a worktable and/or a workfile (it used both for me).
just to make that query take longer on my system I did a cross apply like this in query window 1:
In Query window 2:
EXEC sp_BlitzWho @ExpertMode = 1;
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
Tested with SQL2012 and SQL2016
The text was updated successfully, but these errors were encountered: