Temporarily disable the JSON data type on Azure SQL #36596
Merged
Conversation
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
SamMonoRT
approved these changes
Aug 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
At this specific time, Azure SQL Database does not yet support passing the new JSON data type to the OPENJSON() function; the preview version of SQL Server 2025 does support it. Support is expected to appear very soon on Azure SQL, but we shouldn't take the risk of releasing an rc.1 which is effectively broken on Azure SQL.
This is a one-line, zero-risk PR which temporarily reverts defaulting to the new JSON data type, on Azure SQL only. My expectation is that we'll reenable this for rc.2.
/cc @sampatel @artl93