-
Notifications
You must be signed in to change notification settings - Fork 993
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_BlitzFirst: Wait Stats Details does not display correct number of seconds that the server spent waiting #3507
Labels
Comments
It does. Do a search in the code for "over the last" and you'll see the relevant portions:
If you believe that's incorrect, can you send a screenshot that includes these 3 things:
|
HAHAHA, twelve minutes, good Lord, that's bad. OK, cool, I'll reopen this and get that in, heh. |
BrentOzar
added a commit
that referenced
this issue
May 1, 2024
The headline news result set now shows the accurate number of seconds used for the wait stats sample. Closes #3507.
BrentOzar
added a commit
that referenced
this issue
May 1, 2024
…tats_seconds #3507 sp_BlitzFirst wait stats seconds
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of the script
Look in the stored procedure, and it'll have a version date & number near the top. Put that in here. If it's not the current version (dated in the last month), then upgrade to the current version and test that before reporting a bug - we fix a lot of stuff in each new build. We'll flat out close bug reports for older builds.
What is the current behavior?
This
Details
of the Wait Stats finding displays the@Seconds
variable for how long that the server spent waiting on a particular wait (the default is 5 as shown below):If the current behavior is a bug, please provide the steps to reproduce.
Run
sp_BlitzFirst
on a server busy enough that it takes longer than@Seconds
to run.What is the expected behavior?
This
Details
of the Wait Stats finding should display the number of seconds that it actually spent waiting which in the above example is 122 seconds.Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
Product: Microsoft SQL Server Enterprise: Core-based Licensing (64-bit)
Operating System: Windows Server 2016 Standard (10.0)
Version: 14.0.3465.1
The text was updated successfully, but these errors were encountered: