Add opt-in native string type mappings via behaviour flag (#626).#671
Merged
axellpadilla merged 1 commit intoMay 20, 2026
Merged
Conversation
…). Introduces SQLServerColumnNative which maps STRING -> VARCHAR(MAX), NCHAR -> NCHAR(1), and NVARCHAR -> NVARCHAR(4000). The current default (SQLServerColumn) is unchanged: STRING / NVARCHAR -> VARCHAR(8000), NCHAR -> CHAR(1). Users opt into the new mappings by setting `dbt_sqlserver_use_native_string_types` to True in dbt_project.yml; the new behaviour is intended to become the default in a future release. Fixes a silent non-unicode aliasing of NCHAR / NVARCHAR in the default mappings (now opt-out), and uses NVARCHAR(4000) — the maximum fixed NVARCHAR size — rather than NVARCHAR(8000) which exceeds SQL Server's fixed-length cap.
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.
Introduces SQLServerColumnNative which maps STRING -> VARCHAR(MAX), NCHAR -> NCHAR(1), and NVARCHAR -> NVARCHAR(4000). The current default (SQLServerColumn) is unchanged: STRING / NVARCHAR -> VARCHAR(8000), NCHAR -> CHAR(1).
Users opt into the new mappings by setting
dbt_sqlserver_use_native_string_typesto True in dbt_project.yml; the new behaviour is intended to become the default in a future release.Fixes a silent non-unicode aliasing of NCHAR / NVARCHAR in the default mappings (now opt-out).
Fixes #626