So we added a checked constraint in a migration, but not in the code model. One edge case we for example ran into is that EFCore doesn't support checked constraints yet. With this approach we need to be very careful that every part of the database schema is part of the code model. While this is fine, it seems a bit dangerous. The nuclear option seems to be to delete all migrations and the model snapshot, and creating a new initial migration. We do need to support creating a database from scratch, and updating a database from the last few migrations.

We don't need any rollbacks (we only roll forward), so that makes things more simple. So it's time to clean up some old migrations! But what's the best way to do this? There doesn't seem to be any official guidance on it.

After analysis about 80% of our compile time is spend on the migrations (compiling + Roslyn analyzers). Since EFCore adds a snapshot of the entire db model to every migration, this code adds up quite a bit. After developing our application for a while we've accumulated quite a bit of EFCore database migrations.

Dotnet framework cleanup tool