Provide guidance for deploying migrations · dotnet/EntityFramework.Docs#691

2018-04-24T00:16:11.000Z

This would primarily be: * Best practices (For example, don't run migrations on app startup, generate scripts, etc.) * How to generate scripts * Possibly also how to use ef.exe * How to deploy scripts to common places--e.g. Azure * Possibly pros and cons of doing this a maintenance window as opposed to against a running app, and strategies for doing it against a running app if this is needed.

(5 commentaires) (14 réactions) (0 assignés)PowerShell (1 625 stars) (1 961 forks)batch import

area-migrationshelp wanted

Description

This would primarily be:

Best practices (For example, don't run migrations on app startup, generate scripts, etc.)
How to generate scripts
- Possibly also how to use ef.exe
How to deploy scripts to common places--e.g. Azure
- Possibly pros and cons of doing this a maintenance window as opposed to against a running app, and strategies for doing it against a running app if this is needed.

Guide contributeur

Stack technique: csharpsqlazure
Domaine: documentationbackenddatabase
Type d'issue: documentation
Difficulté: 3
Temps estimé: 1-2 days
Statut d'activité: fresh
Clarté: clear
Prérequis: Basic understanding of Entity Framework migrationsFamiliarity with .NET CLI
Accessibilité débutant: 60
Direction de recherche: Review existing documentation on migrations in the EntityFramework.Docs repo. Write a new page covering best practices for deploying migrations, including how to generate SQL scripts using 'dotnet ef migrations script', and strategies for deploying to Azure. Consider adding a comparison of running migrations during deployment vs. using script generation.