Database Providers

Entity Framework Core can access many different databases through plug-in libraries called database providers.

Current providers


EF Core providers are built by a variety of sources. Not all providers are maintained as part of the Entity Framework Core Project. When considering a provider, be sure to evaluate quality, licensing, support, etc. to ensure they meet your requirements. Also make sure you review each provider's documentation for detailed version compatibility information.

NuGet Package Supported database engines Maintainer / Vendor Notes / Requirements Useful links
Microsoft.EntityFrameworkCore.SqlServer SQL Server 2008 onwards EF Core Project (Microsoft) docs
Microsoft.EntityFrameworkCore.Sqlite SQLite 3.7 onwards EF Core Project (Microsoft) docs
Microsoft.EntityFrameworkCore.InMemory EF Core in-memory database EF Core Project (Microsoft) For testing only docs
Microsoft.EntityFrameworkCore.Cosmos Azure Cosmos DB SQL API EF Core Project (Microsoft) Preview only blog
Npgsql.EntityFrameworkCore.PostgreSQL PostgreSQL Npgsql Development Team docs
Pomelo.EntityFrameworkCore.MySql MySQL, MariaDB Pomelo Foundation Project readme
Pomelo.EntityFrameworkCore.MyCat MyCAT Server Pomelo Foundation Project Prerelease only readme
EntityFrameworkCore.SqlServerCompact40 SQL Server Compact 4.0 Erik Ejlskov Jensen .NET Framework wiki
EntityFrameworkCore.SqlServerCompact35 SQL Server Compact 3.5 Erik Ejlskov Jensen .NET Framework wiki
FirebirdSql.EntityFrameworkCore.Firebird Firebird 2.5 and 3.x Jiří Činčura docs
EntityFrameworkCore.FirebirdSql Firebird 2.5 and 3.x Rafael Almeida wiki
MySql.Data.EntityFrameworkCore MySQL MySQL project (Oracle) docs
Oracle.EntityFrameworkCore Oracle DB 11.2 onwards Oracle Prerelease website
IBM.EntityFrameworkCore Db2, Informix IBM Windows version blog
IBM.EntityFrameworkCore-lnx Db2, Informix IBM Linux version blog
IBM.EntityFrameworkCore-osx Db2, Informix IBM macOS version blog
EntityFrameworkCore.Jet Microsoft Access files Bubi .NET Framework readme
EntityFrameworkCore.OpenEdge Progress OpenEdge Alex Wiese readme
Devart.Data.Oracle.EFCore Oracle DB onwards DevArt Paid docs
Devart.Data.PostgreSql.EFCore PostgreSQL 8.0 onwards DevArt Paid docs
Devart.Data.SQLite.EFCore SQLite 3 onwards DevArt Paid docs
Devart.Data.MySql.EFCore MySQL 5 onwards DevArt Paid docs

Future Providers

Cosmos DB

We have been developing an EF Core provider for the SQL API in Cosmos DB. This will be the first complete document-oriented database provider we have produced, and the learnings from this exercise are going to inform improvements in the design of future releases of EF Core and possibly other non-relational providers. A preview is available on the NuGet Gallery.

Oracle first-party provider

The Oracle .NET team has published the beta of the Oracle provider for EF Core. Please direct any questions about this provider, including the release timeline, to the Oracle Community Site.

Adding a database provider to your application

Most database providers for EF Core are distributed as NuGet packages. This means they can be installed using the dotnet tool in the command line:

dotnet add package provider_package_name

Or in Visual Studio, using NuGet's Package Manager Console:

install-package provider_package_name

Once installed, you will configure the provider in your DbContext, either in the OnConfiguring method or in the AddDbContext method if you are using a dependency injection container. For example, the following line configures the SQL Server provider with the passed connection string:


Database providers can extend EF Core to enable functionality unique to specific databases. Some concepts are common to most databases, and are included in the primary EF Core components. Such concepts include expressing queries in LINQ, transactions, and tracking changes to objects once they are loaded from the database. Some concepts are specific to a particular provider. For example, the SQL Server provider allows you to configure memory-optimized tables (a feature specific to SQL Server). Other concepts are specific to a class of providers. For example, EF Core providers for relational databases build on the common Microsoft.EntityFrameworkCore.Relational library, which provides APIs for configuring table and column mappings, foreign key constraints, etc. Providers are usually distributed as NuGet packages.


When a new patch version of EF Core is released, it often includes updates to the Microsoft.EntityFrameworkCore.Relational package. When you add a relational database provider, this package becomes a transitive dependency of your application. But many providers are released independently from EF Core and may not be updated to depend on the newer patch version of that package. In order to make sure you will get all bug fixes, it is recommended that you add the patch version of Microsoft.EntityFrameworkCore.Relational as a direct dependency of your application.