Always Encrypted encrypts SQL Server columns on the client, so the database engine never sees their plaintext. Secure enclaves can run some otherwise blocked query operations inside a protected environment. The article walks through choosing an encryption type, defining the column and configuring a .NET client.
A write-up on Tilly POS, a multi-branch point-of-sale built with ASP.NET Core 10, EF Core and SQL Server, explains how three costly failures were designed out: double charges, half-written sales and overselling. The fixes are practical: idempotency keys backed by a unique index, one transaction per sale, and a single conditional UPDATE for stock. Useful for any .NET service that moves money or inventory.
A developer moving from Spring Boot to EF Core explains how SQL Server's rowversion differs from JPA's @version field. The value comes from a database-wide counter, so it is not a per-row version number. This matters for .NET developers who need to set up optimistic concurrency correctly.
SQL Server error 1934 appears when a statement uses a feature such as a filtered index while the session has QUOTED_IDENTIFIER off. The author explains why the ASP.NET Core application never sees it while the classic sqlcmd does, and how the setting interacts with stored procedures. Useful for anyone who updates ASP.NET Core Identity tables by hand.