How does one check that a database contains the schema for the current model?

[SolalPirelli]

Question

Some low-level APIs explicitly call out that they perform no schema validation, such as DatabaseFacade.EnsureCreated:

If the database exists and has any tables, then no action is taken. Nothing is done to ensure the database schema is compatible with the Entity Framework model.

As well as HasTables and Exists on IRelationalDatabaseCreator:

No attempt is made to determine if tables belong to the current model or not.

Such wording implies there should be a way to validate that a database conforms to the current schema, but I couldn't find how to do that. Is checking for the absence of pending migrations enough?

For context, my use case is that I have a website using a SQLite database, and I want to let users export and import backups of the entire database as a file. Before overwriting the local database with a user-provided backup, I'd like to check that said backup actually did come from the system rather than the user accidentally uploading the wrong file and destroying everything.

Your code

Stack traces

Verbose output

EF Core version

10.0.3

Database provider

Microsoft.EntityFrameworkCore.Sqlite

Target framework

.NET 10

Operating system

Windows 11

IDE

VS 2026

[roji]

Is checking for the absence of pending migrations enough?

Assuming you're using migrations properly, yes. EF records which migrations have been applied in a history table, and uses that to know whether any new migrations (in the application) haven't yet been applied to the database; assuming you don't change your database schema outside of EF's migration process, this works. The alternative would be for EF to go over every table and column in the database, and also over every facet of those database objects, which is both unfeasible (some facets/details simply can't be introspected in some databases) and potentially quite slow.

For context, my use case is that I have a website using a SQLite database, and I want to let users export and import backups of the entire database as a file. Before overwriting the local database with a user-provided backup, I'd like to check that said backup actually did come from the system rather than the user accidentally uploading the wrong file and destroying everything.

Well, you can indeed check that the new SQLite database has all the expected migrations applied to it (i.e. that you haven't added new migrations to the application which are missing from the user's incoming database) - that should work.

[SolalPirelli]

OK, thanks!