Start Debugging

Tag: sql-server

25 posts · Page 1 of 3

2026-09-27 ef-core ef-core-11 sql-server

How to add a unique index on a JSON-mapped property in EF Core 11 (SQL Server and SQLite)

HasIndex(...).IsUnique() on a ToJson() member does not enforce uniqueness in EF Core 11 RC 1: SQL Server drops IsUnique and SQLite indexes the whole document. Expose the JSON value as a computed column and put the unique index on that instead.

2026-09-20 ef-core ef-core-11 concurrency

How to guarantee idempotent message processing with EF Core 11 when two app instances consume the same message

The existence check in your handler is not the guard you think it is. Put a unique index on the inbox table, write the marker in the same SaveChanges as the business change, and let the database pick the winner. Plus the ExecuteUpdate trap that quietly undoes all of it.

2026-09-19 ef-core ef-core-11 migrations

How to apply custom naming conventions for primary keys, foreign keys, and indexes in EF Core 11 migrations

Rename every PK_, FK_, AK_ and IX_ that EF Core 11 generates with one IModelFinalizingConvention, keep explicit names winning, stay under the identifier length limit, and avoid the clustered-index rebuild the next migration scaffolds on an existing database.

2026-09-17 comparison dotnet dotnet-11

Microsoft.Data.SqlClient vs System.Data.SqlClient in .NET 11

Use Microsoft.Data.SqlClient. System.Data.SqlClient is deprecated, already emits CS0618 on every type you touch, and loses its .NET assets when .NET 8 goes end of support on November 10, 2026, the same day .NET 11 ships. The measured feature gap, the Encrypt default that breaks the migration, and the 7.0 package split.

2026-09-16 comparison ef-core ef-core-11

SQL Server compatibility level 150 vs 160: what changes for EF Core 11 queries

EF Core 11 now defaults UseSqlServer to compatibility level 160, which puts LEAST, GREATEST and two-argument LTRIM/RTRIM into your SQL, including every Take(n).FirstOrDefault(). Keep 160 on SQL Server 2022 and later; pin UseCompatibilityLevel(150) if any environment still runs SQL Server 2019.

2026-09-15 errors ef-core ef-core-11

Fix: EF Core MigrateAsync and CanConnectAsync keep retrying on 'Login failed for user' for 60 seconds

EF Core's SQL Server existence check retries error 18456 for a full minute, with or without EnableRetryOnFailure. Fail fast, cap RetryTimeout, or wait for EF Core 12.

2026-09-14 errors ef-core ef-core-11

Fix: Could not load file or assembly 'Microsoft.Data.SqlClient, Version=7.0.0.0' after updating EF Core

EF Core 11 is compiled against Microsoft.Data.SqlClient 7.0.0.0, but a 6.x copy won the restore or the deploy. Remove the old SqlClient pin and redeploy the full output.

2026-09-12 ef-core ef-core-11 dotnet-11

How to escape % and _ wildcards in EF.Functions.Like and StartsWith queries in EF Core 11

StartsWith, EndsWith and Contains already escape % and _ for you in EF Core 11, but EF.Functions.Like does not. Here is the SQL EF generates, a reusable escape helper, and the escapeCharacter overload that makes it work on SQL Server, SQLite and PostgreSQL.

2026-09-12 comparison ef-core ef-core-11

Native json column vs nvarchar(max) for storing JSON in SQL Server with EF Core 11

Use the native json type on SQL Server 2025 and Azure SQL: EF Core 11 gets JSON_CONTAINS, typed JSON_VALUE, in-place modify() and JSON indexes out of it. Stay on nvarchar(max) for SQL Server 2019/2022, legacy tooling, or a schema you must be able to roll back.

2026-09-09 errors ef-core ef-core-11

Fix: AS JSON option can be specified only for column of nvarchar(max) type in WITH clause

EF Core emits [col] json '$.path' AS JSON inside OPENJSON WITH, which Azure SQL rejects with Msg 13618. Upgrade to EF Core 10.0.11+, or drop the provider compatibility level to 160.