Document SQL Server compatibility level bump#5352
Merged
Conversation
roji
force-pushed
the
roji/sql-server-compatibility
branch
3 times, most recently
from
c9f9ea3 to
ab811f9
Compare
Document dotnet/efcore#38198 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
roji
force-pushed
the
roji/sql-server-compatibility
branch
from
ab811f9 to
2538499
Compare
AndriySvyryd
approved these changes
May 7, 2026
There was a problem hiding this comment.
Pull request overview
This PR updates the EF Core documentation to call out a SQL Server provider behavior change: the default SQL Server compatibility level used by UseSqlServer is bumped to 160, which enables SQL Server 2022-specific translations by default.
Changes:
- Added a short “Other changes” note in the EF Core 11 SQL Server what’s-new page referencing the new default compatibility level and pointing to the breaking change entry.
- Added a new EF Core 11 breaking-change entry documenting the default compatibility level change, its impact, and mitigations.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md | Adds a brief SQL Server “Other changes” note highlighting the new default compatibility level and linking to the breaking change entry. |
| entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md | Adds a new breaking-change entry documenting the default compatibility level change and mitigation guidance. |
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
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.
Documents dotnet/efcore#38198.
Adds an EF Core 11 breaking-change entry for the SQL Server default compatibility level changing from 150 to 160, and a brief SQL Server what's-new note highlighting the SQL Server 2022 translation changes enabled by default.