Performance counters fix for version 2022 and overall formatting (XTP rebuilded) #213
Conversation
This file contains 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
Some counters didn't had SQL 2022 version option yet.
…w from scratch SQL Versions 2017 and 2019 have the same counters named 2017 SQL 2016 don't have 3 counters present on the other versions
PiJoCoder
approved these changes
Nov 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes # .
Performance counters fix for version 2022 and overall formatting (XTP rebuilded)
Changes proposed in this pull request:
Performance counters fix for version 2022 and overall formatting (XTP rebuilded)
How to test this code:
Execute pssdiag and open counters file
Has been tested on (remove any that don't apply):