Export-DbaUser - Use server version instead of db compat level for scripting#10344
Merged
potatoqualitee merged 1 commit intodevelopmentfrom Apr 15, 2026
Merged
Conversation
…ripting When no -DestinationVersion is specified, use the actual SQL Server instance version (VersionMajor) rather than the database compatibility level as the SMO scripting target. This fixes an error where databases on newer SQL Server instances (e.g., 2022) with a lower compatibility level (e.g., 120/SQL2014) could not export users that use features not available at the compat level, such as External users introduced in SQL Server 2016. Fixes #10343 (do Export-DbaUser) Co-authored-by: Andreas Jordan <andreasjordan@users.noreply.github.com>
Member
|
Very nice thank you |
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
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.
When no -DestinationVersion is specified, use the actual SQL Server instance version rather than the database compatibility level as the SMO scripting target. This fixes an error where databases on newer SQL Server instances (e.g., 2022) with a lower compatibility level (e.g., 120/SQL2014) could not export users that use features not available at the compat level, such as External users introduced in SQL Server 2016.
Fixes #10343
Generated with Claude Code