sp_BlitzIndex: Added reports of resumable index operations (closes #3609 ) #3619
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e mode 0 and mode 4 outputs, as well as the mode where you name one table. The priority set here is very high, but that seems correct. They can prevent DDL! Not included: Any reference to the 2022 feature that auto-kills paused indexes. It is in the ALTER DATABASE SCOPED CONFIGURATION docs. I will make an issue for it.
Member
|
Looks good! Tested in my lab, works. Thanks for the pull request, merging into the dev branch, will be in the next release with credit to you in the release notes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added reports of resumable index operations to the mode 0 and mode 4 outputs, as well as the mode where you name one table. The priority set here is very high, but that seems correct. They can prevent DDL!
Brent warned that I should check if the
sys.index_resumable_operationshonoursNOLOCK, but as far as I can tell it's impossible to put a resumable operation in a transaction.My production experience of resumable operations is very limited, so the warnings that I have given about them relied on either trusting the documentation or doing what I could easily verify. If there are much nastier things to warn of, then somebody should change my strings.
I think that this is my first contribution to
sp_BlitzIndex. It is certainly my first non-trivial one. All of my testing says that I've done the work correctly. However, you shouldn't trust a first timer.Not included: Any reference to the 2022 feature that auto-kills paused indexes. It is in the ALTER DATABASE SCOPED CONFIGURATION docs. I will make an issue for it.