Test-DbaDbRecoveryModel: Fix for instances with case sensitive collation #9425
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
I was getting the following results on a system with a case sensitive collation WARNING: [19:42:15][Test-DbaDbRecoveryModel] Error occurred while establishing connection to xxxxxxxxxx | The multi-part identifier "d.recovery_model" could not be bound. The multi-part identifier "d.name" could not be bound. The multi-part identifier "d.recovery_model" could not be bound. The multi-part identifier "d.recovery_model_desc" could not be bound. The multi-part identifier "d.recovery_model" could not be bound.
andreasjordan
changed the title
andreasjordan
approved these changes
Jul 20, 2024
|
Thank you very much! And welcome 😊 |
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.
I was getting the following results on a system with a case sensitive collation (Latin1_General_100_CS_AS)
WARNING: [19:42:15][Test-DbaDbRecoveryModel] Error occurred while establishing connection to xxxxxxxxxx | The multi-part identifier "d.recovery_model" could not be bound. The multi-part identifier "d.name" could not be bound. The multi-part identifier "d.recovery_model" could not be bound. The multi-part identifier "d.recovery_model_desc" could not be bound. The multi-part identifier "d.recovery_model" could not be bound.
Type of Change
.\tests\manual.pester.ps1)Purpose
Be able to use dbacheck "PseudoSimple" that uses this dbatool function
Approach
Using the same casing for the table alias will resolve any casing issues with case sensitive collations.L