Issue with recommendation (or the very existence of this product)

[xavier-90]

I quote: "Carefully consider before using this approach in production. Experience has shown that the simplicity of this deployment strategy is outweighed by the issues it creates. Consider using SQL scripts instead."

So what is the raison d'etre of this product? What is the point in spending any time at all developing migration scripts if ultimately we also have to spend time developing SQL scripts to migrate production servers?

I understand the caution and the recommendation not to include the scripts in the primary application but surely the migration mechanism can form part of a separate application/process to upgrade production servers under controlled conditions?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 06b35eff-79e4-2068-6d1c-f9079d43f903
• Version Independent ID: 6c575b10-048c-349c-397e-0d9c11d47235
• Content: Applying Migrations - EF Core
• Content Source: entity-framework/core/managing-schemas/migrations/applying.md
• Product: entity-framework
• Technology: entity-framework-core
• GitHub Login: @bricelam
• Microsoft Alias: bricelam

[ErikEJ]

@xavier-90 the tooling creates the SQL script for you.