Set-DbaDbCompatbility - Fix for using piped input and don't trust master compatibility level #9146
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
|
solid change 💪🏼 |
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.
Type of Change
.\tests\manual.pester.ps1)Experienced this bug today at a client wihle doing
Get-DbaDatabase -SqlInstance sql01 | Where-Object Name -like Test* | Set-DbaDbCompatibility.If we support pipeline input, we must not use $SqlInstance. And every database can be on a different server with a different server level. So we can only get the server level inside of the loop for every individual database. And I used the same method to get the server level like in Test-DbaDbCompatibility (see #8992 for details).