Inclusive language changes for sp_BlitzIndex #3582
Merged
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
BrentOzar
approved these changes
Oct 19, 2024
Member
BrentOzar
left a comment
BrentOzar
left a comment
There was a problem hiding this comment.
Thanks for the pull request! I really appreciate how much work this was. Looks good, works on my machines, 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.
Hey Brent!
I've updated the wording in sp_BlitzIndex for:
I've also updated the list in sp_BlitzIndex_Checks_by_Priority.md
Note that I couldn't find check_id 12 anywhere in sp_BlitzIndex nor anything else pointing to "Aggressive Indexes" aside from check_id 11,
Closes #3571