This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
EF Core provides two primary ways of keeping your EF Core model and database schema in sync. To choose between the two, decide whether your EF Core model or the database schema is the source of truth.
If you want your EF Core model to be the source of truth, use Migrations. As you make changes to your EF Core model, this approach incrementally applies the corresponding schema changes to your database so that it remains compatible with your EF Core model.
Use Reverse Engineering if you want your database schema to be the source of truth. This approach allows you to scaffold a DbContext and the entity type classes by reverse engineering your database schema into an EF Core model.
Note
The create and drop APIs can also create the database schema from your EF Core model. However, they are primarily for testing, prototyping, and other scenarios where dropping the database is acceptable.
.NET feedback
.NET is an open source project. Select a link to provide feedback:
Training
Module
Persist and retrieve relational data by using EF Core - Training
This module guides you through the steps to create a data access project. You connect to a relational database and construct create, read, update, and delete (CRUD) queries by using Entity Framework Core (EF Core).
Documentation
Create and Drop APIs - EF Core
APIs for creating and dropping databases with Entity Framework Core
Adding, removing and otherwise managing database schema migrations with Entity Framework Core
Overview of using migrations to manage database schemas with Entity Framework Core
