Migrations in Prod and Raw SQL

1. What is the first step in the pipeline for safely deploying schema changes in production?

Migrations live in source control Generate a deployment script Apply migrations on app startup Design for zero-downtime

2. Why should you never use `Database.Migrate()` on application startup in production?

It slows down application startup It creates multiple instances trying to migrate simultaneously It automatically rolls back failed migrations It requires additional database privileges

3. When needing to perform bulk updates or deletes, what is a valid reason to drop to raw SQL?

EF translates all LINQ perfectly Stored procedures cannot be audited Set-based operations are more efficient Raw SQL can be hard-coded

4. What should be done if a column needs to be renamed in a live table?

Rename the column directly Use a two-release dance for the change Drop the column and create a new one Modify the original migration file

Continue: Design an Endpoint → Review this lesson Retake quiz