SQL Server Collations In EF Core

EF6 and multiple configurations (SQL Server and SQL Server Compact)

Update:... Problem solved, see end of this question....The problem...:...We are trying to use Entity Framework 6 and code-based configuration in a scenario were we have use both a SQL Server and SQL Server CE in the same ...AppDomain.......This quite simple scenario seems not to be supported "by design". From the EF team:...Note: We do not support ...

Column encryption in ASP MVC app with SQL Server 2016 using .net Core / EF Core

I am trying to use the "Always Encrypted" feature in SQL Server 2016 to encrypt some columns. I used ...this post... as a guide to set the columns as encrypted in SSDT....That part goes fine, it's when I attempt to query the data from the application that I get an error. According to the docs I need to add this:...column encryption setting=enabled ...

EF Core migrations using asp.net core, SQL Server and Docker yields dotnet SDK error

microsoft/aspnetcore:1.1.0... your are using is based on ...microsoft/dotnet:1.1.0-runtime.... It contains only .NET Core runtime, not SDK. To execute commands like ...run..., ...ef... and other tools - you need ...one of ...sdk...-based images

EF Core HasComputedColumnSql - computed on Insert/Update or each query on SQL Server / AzureSQL?

Good question. It's unclear from EF Core documentation what type of computed column does ...HasComputedColumnSql... represent. Probably because it's a part of the relational extensions, thus is considered provider specific. But since it has no configuration options, I agree that the behavior should be specified....A quick test with SQL Server shows...

How to revert EF Core migration from SQL Server 2016 production machine

You can generate the SQL script to revert a migration using the ...Script-Migration... or ...dotnet ef migrations script... command....dotnet ef migrations script TheAppliedMigration TheMigrationBeforeIt -o revert.sql

EF Core Migration with multiple provider always runs SQL Server scripts

In my case, I use the same migration for both providers but sometimes I need to do some changes to migration files manually. for example added annotation for both providers (or change the type of some fields like ...varchar... to ...nvarchar...)....Id = table.Column<int>(nullable: false) .Annotation("MySql:ValueGeneratedOnAdd", true) ...

SQL query to LINQ expression - Entity Core Framework 3 + SQL Server

You need to use the singleton ...GroupBy... trick:...var ans = ThisAwesomeTable.GroupBy(r => 1) .Select(rg => new { lessThan30 = rg.Sum(r => r.CreatedWhen >= thirtyDaysAgo ? 1 : 0), GreaterThan30 = rg.Sum(r => r.CreatedWhen < thirtyDaysAgo ? 1 : 0) ...

Cannot Execute SQL Server SP with Named and output parameters using EF Core

The issue is that the parameters are going to be provided to the sp in the order in which they are received. You want to assign them to the sp using the names in the sp, which can be the same....The sql executed will essentially be this:...declare @I_vITEMNMBR char(30) = .. , @I_vLOCNCODE char(10) = .., @I_vUOFM char(8) = .., @I_vBIN...

Getting "NEXT VALUE FOR" for a SQL Server sequence using EF Core 3.1 - impossible?

I'm writing a new ASP.NET Core Web API, and one of my requirements is to be able to leverage EF Core 3.1 to grab the next value of a ...sequence... defined in my SQL Server as the ID for a record I need to store....I'm struggling to find a way to do this - in EF 6.x, I used a method directly on the ...DbContext... descendant like this:...public int...

Specify Azure SQL server edition in EF Core without breaking local development

Of course ...EDITION... and ...SERVICE_OBJECTIVE... are not supported for non Azure SQL Database....You need to run your commands only for Azure database. For other types of SQL server you need to miss execution of your code....I suggest to detect ...SQL Server Edition... before running your code....For this purpose you can add extension method:...