sp_BlitzFirst: "Garbage Collection in Progress" warning can be triggered by memory-optimized TempDB #3488
Comments
BrentOzar
added a commit
that referenced
this issue
Apr 15, 2024
Clarifying warning that can also be caused by memory-optimized TempDB. Closes #3488.
BrentOzar
added a commit
that referenced
this issue
Apr 15, 2024
…e_collection #3488 sp_BlitzFirst garbage collection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
If you turn on memory-optimized TempDB, sp_BlitzFirst will return the warning "Garbage Collection in Progress" warning. Need to add more advice to the warning that one of the sources could be TempDB.
Describe the solution you'd like
Just add text to the existing warning.
Describe alternatives you've considered
Adding text to the URL with more info, but... people don't read.
Are you ready to build the code for the feature?
I'm on it!
The text was updated successfully, but these errors were encountered: