Skip to content

Bump default SQL Server compat level to 160 (SQL Server 2022) #38199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
roji wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Bump default SQL Server compat level to 160 (SQL Server 2022) #38199

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
05a9cbe
Bump default SQL Server compat level to 160 (SQL Server 2022)
roji Apr 30, 2026
e7fed49
Refactor SQL Server tests
roji Apr 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions src/EFCore.SqlServer/Infrastructure/Internal/SqlServerOptionsExtension.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,8 @@ public class SqlServerOptionsExtension : RelationalOptionsExtension, IDbContextO
private int? _azureSynapseCompatibilityLevel;
private bool _useRetryingStrategyByDefault;

// For the SQL Server/Azure SQL compatibility levels, see
// https://learn.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-compatibility-level
// SQL Server 2025 (17.x): compatibility level 170 (default for Azure SQL, currently preview for on-prem)
// SQL Server 2025 (17.x): compatibility level 170, start date 2025-11-18, mainstream end date 2031-01-06, extended end date 2036-01-06
// SQL Server 2022 (16.x): compatibility level 160, start date 2022-11-16, mainstream end date 2028-01-11, extended end date 2033-01-11
// SQL Server 2019 (15.x): compatibility level 150, start date 2019-11-04, mainstream end date 2025-02-28, extended end date 2030-01-08
// SQL Server 2017 (14.x): compatibility level 140, start date 2017-09-29, mainstream end date 2022-10-11, extended end date 2027-10-12
Expand All @@ -36,7 +35,7 @@ public class SqlServerOptionsExtension : RelationalOptionsExtension, IDbContextO
/// any release. You should only use it directly in your code with extreme caution and knowing that
/// doing so can result in application failures when updating to a new Entity Framework Core release.
/// </summary>
public static readonly int SqlServerDefaultCompatibilityLevel = 150;
public static readonly int SqlServerDefaultCompatibilityLevel = 160;

Comment thread
roji marked this conversation as resolved.
/// <summary>
/// This is an internal API that supports the Entity Framework Core infrastructure and not subject to
Expand Down
2 changes: 1 addition & 1 deletion src/EFCore.SqlServer/Infrastructure/SqlServerDbContextOptionsBuilder.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ public virtual SqlServerDbContextOptionsBuilder EnableRetryOnFailure(

/// <summary>
/// Sets the SQL Server compatibility level that EF Core will use when interacting with the database. This allows configuring EF
/// Core to work with older (or newer) versions of SQL Server. Defaults to <c>150</c> (SQL Server 2019).
/// Core to work with older (or newer) versions of SQL Server. Defaults to <c>160</c> (SQL Server 2022).
/// </summary>
/// <remarks>
/// See <see href="https://aka.ms/efcore-docs-dbcontext-options">Using DbContextOptions</see>, and
Expand Down
Loading
Loading