migration-check

Validate EF Core migrations for destructive operations by detecting dropped columns, NOT NULL additions without defaults, and data-destructive renames before they impact production during pre-deploy reviews.

EF Core migration downtime risks include new indexes on large tables, foreign key additions, and computed column additions. Validating these risky operations before deployment prevents unexpected production outages.

Safely renaming columns requires two-phase patterns to maintain backward compatibility. This involves applying incremental migration changes sequentially so older application versions continue functioning during deployment.

Adding NOT NULL constraints without defaults causes downtime. Apply two-phase patterns by first adding the column as nullable, backfilling data, and then enforcing the constraint in a subsequent migration.

Yes, migration validation integrates directly with the dotnet ef migrations workflow. You can validate a pending migration like 'AddTenantScope' to automatically check for safe, risky, and destructive operations.

Safe EF Core schema operations include adding new nullable columns and creating entirely new tables. These operations are flagged as safe because they avoid modifying existing data structures and prevent backward compatibility issues.