dotnet:migration-check

To check EF Core migrations for downtime risks, you validate the migration file to identify destructive operations like dropped columns, NOT NULL additions without defaults, and data-destructive renames that can break your application.

Database migration changes that cause data loss in Entity Framework Core include dropped columns, data-destructive renames, and NOT NULL additions without default values, which this validation process detects and categorizes for review.

Validating backward compatibility for EF Core database migrations involves ensuring migrations can be reversed successfully and do not violate existing data integrity, preventing application breaks during deployment.

Yes, you need the EF Core CLI to validate database migration files, as it manages migration states and applies changes within a controlled environment to assess downtime and data loss risks.

The best way to prevent downtime when adding indexes to large tables in EF Core is to run a downtime risk assessment that evaluates operations requiring full table rewrites and provides recommended mitigation steps.

Adding a foreign key in EF Core migration requires a downtime risk assessment because foreign key additions and computed columns can require full table rewrites, potentially causing significant downtime and backward compatibility issues.