Document SQL Server compatibility level bump

Document dotnet/efcore#38198

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Shay Rojansky

entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md

@@ -23,6 +23,7 @@ This page documents API and behavior changes that have the potential to break ex
 |:--------------------------------------------------------------------------------------------------------------- | -----------|
 | [Sync I/O via the Azure Cosmos DB provider has been fully removed](#cosmos-nosync)                              | Medium     |
 | [Microsoft.Data.SqlClient has been updated to 7.0](#sqlclient-7)                                                | Medium     |
+| [SQL Server compatibility level now defaults to 160](#sqlserver-compatibility-level-160)                       | Low        |
 | [EF Core now throws by default when no migrations are found](#migrations-not-found)                             | Low        |
 | [`EFOptimizeContext` MSBuild property has been removed](#ef-optimize-context-removed)                           | Low        |
 | [EF tools packages no longer reference Microsoft.EntityFrameworkCore.Design](#ef-tools-no-design-dep)           | Low        |
@@ -85,6 +86,39 @@ No code changes are required beyond adding this package reference. If you use `S
 
 ## Low-impact changes
 
+<a name="sqlserver-compatibility-level-160"></a>
+
+### SQL Server compatibility level now defaults to 160
+
+[Tracking Issue #38198](https://github.com/dotnet/efcore/issues/38198)
+
+#### Old behavior
+
+Previously, when using <xref:Microsoft.EntityFrameworkCore.SqlServerDbContextOptionsExtensions.UseSqlServer*> without explicitly configuring a SQL Server compatibility level, EF Core defaulted to compatibility level 150, corresponding to SQL Server 2019.
+
+#### New behavior
+
+Starting with EF Core 11.0, <xref:Microsoft.EntityFrameworkCore.SqlServerDbContextOptionsExtensions.UseSqlServer*> defaults to compatibility level 160, corresponding to SQL Server 2022. This allows EF to generate SQL which uses SQL Server 2022 features by default. For example, some queries now use `LEAST` and `GREATEST`, including translations for `Math.Min`, `Math.Max`, <xref:Microsoft.EntityFrameworkCore.RelationalDbFunctionsExtensions.Least*>, <xref:Microsoft.EntityFrameworkCore.RelationalDbFunctionsExtensions.Greatest*>, and some `Take`/`Skip` patterns.
+
+If your database runs on SQL Server 2019 or older, or is configured with a compatibility level lower than 160, some SQL generated by EF Core may no longer be supported by the database.
+
+#### Why
+
+SQL Server 2022 has been available for several years, and using compatibility level 160 by default allows EF Core to generate simpler and more efficient SQL for newer SQL Server versions.
+
+#### Mitigations
+
+If your database does not support compatibility level 160, configure EF Core to use the compatibility level supported by your database:
+
+```csharp
+protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
+{
+    optionsBuilder.UseSqlServer("<connection string>", o => o.UseCompatibilityLevel(150));
+}
+```
+
+For more information, see the [SQL Server compatibility level documentation](xref:core/providers/sql-server/index#compatibility-level).
+
 <a name="migrations-not-found"></a>
 
 ### EF Core now throws by default when no migrations are found

entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md

@@ -262,6 +262,23 @@ For the full `JSON_PATH_EXISTS` SQL Server documentation, see [`JSON_PATH_EXISTS
 
 ## SQL Server
 
+<a name="sql-server-compatibility-level-160"></a>
+
+### Default compatibility level changed to SQL Server 2022
+
+When using <xref:Microsoft.EntityFrameworkCore.SqlServerDbContextOptionsExtensions.UseSqlServer*> without explicitly configuring a SQL Server compatibility level, EF Core now defaults to compatibility level 160 (SQL Server 2022), rather than 150 (SQL Server 2019). This enables SQL Server 2022-specific SQL translations by default.
+
+For example, `Math.Min`, `Math.Max`, <xref:Microsoft.EntityFrameworkCore.RelationalDbFunctionsExtensions.Least*>, <xref:Microsoft.EntityFrameworkCore.RelationalDbFunctionsExtensions.Greatest*>, and `Min`/`Max` over inline or primitive collections can now translate to `LEAST` and `GREATEST` by default. EF can also use `LEAST` to simplify some queries with multiple `Take` operators, or with `Skip` and `Take`:
+
+```sql
+SELECT [c].[CustomerID], [c].[ContactName]
+FROM [Customers] AS [c]
+ORDER BY [c].[ContactTitle], [c].[ContactName]
+OFFSET @p ROWS FETCH NEXT LEAST(@p1, @p2) ROWS ONLY
+```
+
+If your database is SQL Server 2019 or older, or has a compatibility level lower than 160, configure EF's SQL Server compatibility level explicitly. For more information, see the [breaking change note](xref:core/what-is-new/ef-core-11.0/breaking-changes#sqlserver-compatibility-level-160) and the [SQL Server provider documentation](xref:core/providers/sql-server/index#compatibility-level).
+
 <a name="sqlserver-vector-search"></a>
 
 ### VECTOR_SEARCH() and vector indexes