blocks|key|576671|text|您有几个选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|576672|576673|您可以使用update-database+-script生成SQL命令来更新服务器上的数据库|unordered-list-item|offset|length|style|CODE|576674|您可以使用驻留在/packages/EntityFramework5.0.0/tools/migrate.exe上的包文件夹中的migrate.exe可执行文件。|576675|如果你使用IIS+Web+deploy，你可以告诉服务器在发布后执行迁移(见下图)|576676|你可以设置自动迁移，但我更喜欢控制何时发生:)|576677|576678|更新：另外，请查看Sayed+Ibrahim's+blog，他在微软的MsBuild团队工作，在部署方面有一些很好的见解|BOLD|576679|​|576680|📷|atomic|576681|576682|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9705241/what-is-the-correct-format-for-running-entity-framework-migrate-exe-tool-without|1|http://sedodream.com/2012/08/06/PlansRegardingWebsiteProjectsAndWebDeploymentProjects.aspx|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0fd37cd9e12d22556a6e5b7d7852bc3e.png|imageAlt^0|0|0|5|N|0|8|1C|1S|B|0|0|0|0|0|0|3|9|K|1|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1H|8|@$F|1I|G|1J|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1K|8|@$F|1L|G|1M|H|I]]|9|@$F|1N|G|1O|1|1P]]|A|$]]|$1|L|3|M|5|E|7|1Q|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1R|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1T|8|@$F|1U|G|1V|H|S]]|9|@$F|1W|G|1X|1|1Y]]|A|$]]|$1|T|3|U|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|20|8|@]|9|@$F|21|G|22|1|23]]|A|$]]|$1|Y|3|U|5|6|7|24|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]|17|$5|12|13|14|A|$15|18]]|19|$5|1A|13|1B|A|$1C|1D|1E|-4]]]]

You have a couple of options:

<ul>
<li>You could use <code>update-database -script</code> to generate the SQL commands to update the database on the server</li>
<li>You could use the <a href="https://stackoverflow.com/questions/9705241/what-is-the-correct-format-for-running-entity-framework-migrate-exe-tool-without">migrate.exe</a> executable file that resides in the package folder on <code>/packages/EntityFramework5.0.0/tools/migrate.exe</code>. I've used it successfully in the past with Jet Brains' Team City Build Server to setup the migrations with my deploy scripts.</li>
<li>If you're using IIS Web Deploy you can tell the server to perform the migrations after publish (see pic below)</li>
<li>You could setup automatic migrations, but I prefer to be in control of when things happen :)</li>
</ul>

Update: Also, check out <a href="http://sedodream.com/2012/08/06/PlansRegardingWebsiteProjectsAndWebDeploymentProjects.aspx" rel="noreferrer">Sayed Ibrahim's blog</a>, he works on the MsBuild Team at Microsoft and has some great insights on deployments 

<img src="https://i.stack.imgur.com/1p4gN.png" alt="enter image description here">

blocks|key|1719494|text|我知道这个问题已经回答了，但供将来参考：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1719495|其中一种选择是在DB上下文类的构造函数中放入如下内容：|1719496|public+MyDbContext()
++++{
++++++++System.Data.Entity.Database.SetInitializer(new+MigrateDatabaseToLatestVersion<MyDbContext,+Configuration>());++++++++++++
++++}|code-block|syntax|javascript|1719497|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I know that the question is already answered, but for future reference:

One of the options is to put something like this in the constructor of your DB context class:

<pre><code>public MyDbContext()
 {
 System.Data.Entity.Database.SetInitializer(new MigrateDatabaseToLatestVersion&lt;MyDbContext, Configuration&gt;()); 
 }
</code></pre>

blocks|key|1717696|text|对我们来说，DBA是唯一有权访问生产(和生产前)环境的组。我们只需使用Sql包控制台命令来获取更新数据库所需的Update-Database+-Script。这将移交给他们，他们可以验证它，等等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1717697|对一些人来说可能有点过于简单化了，但它是有效的。|1717698|HTH。|1717699|entityMap^0|1J|N|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

For us, the DBAs are the only group to have access to the production (and pre-production) environments. We simply use the <code>Update-Database -Script</code> package console command to get the Sql required to update the database. This gets handed off to them where they can validate it, etc.

Maybe a little too simplistic for some but it works.

HTH.

blocks|key|3912901|text|一个简单的解决方案:从本地Package+Manager控制台运行Update-Database，为生产连接字符串提供一个连接字符串参数。您还必须提供连接提供程序名称(此示例代码中的SqlServer)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3912902|Update-Database+-ConnectionString+<your+real+remote+server+connection+string+here>+-ConnectionProviderName+System.Data.SqlClient|code-block|syntax|javascript|3912903|您可以使用app.config文件connectionStrings部分中的连接字符串名称来代替连接字符串：|3912904|Update-Database+-ConnectionStringName+<your+connection+string+name+here>|3912905|您必须具有从本地计算机访问该服务器的权限。例如，如果您能够从Sql+server+Management+Studio连接到服务器，则可以使用此命令。|3912906|请注意，对于实际的生产系统，不建议使用这种方法，您应该使用类似于公认答案中解释的内容。但在开发远程服务器、测试环境等方面，它可以帮助您快速破解。|3912907|entityMap^0|X|F|0|0|H|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|13|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

A simple solution: running <code>Update-Database</code> from your local Package Manager Console providing a connection string parameter with the production connection string. You also have to provide the connection provider name (SqlServer in this example code):

<pre><code>Update-Database -ConnectionString &lt;your real remote server connection string here&gt; -ConnectionProviderName System.Data.SqlClient
</code></pre>

Instead of the connection string you can use a connection string name present in your app.config file <code>connectionStrings</code> section:

<pre><code>Update-Database -ConnectionStringName &lt;your connection string name here&gt;
</code></pre>

You must have permissions to access that server from your local machine. For example, if you are able to connect to the server from a Sql Server Management Studio you can use this.

Note that this approach is not recommended for a real production system, you should use something like what is explained in the accepted answer. But it can help you with quick hacks in development remote servers, test environments, etc.

blocks|key|1788107|text|我个人喜欢设置在每次调用应用程序的start方法时运行的自动迁移。这样，对于您进行的每个部署，您只需运行迁移并自动更新应用程序即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1788108|看看这篇来自AppHarbor的文章。http://blog.appharbor.com/2012/04/24/automatic-migrations-with-entity-framework-4-3|offset|length|1788109|要点是，您希望启用自动迁移，然后从代码中调用DatabaseInitializer，或者从OnModelCreating方法调用，或者从Global.asax调用。|1788110|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.appharbor.com/2012/04/24/automatic-migrations-with-entity-framework-4-3^0|0|J|2B|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I personally like to setup automatic migrations that run every time the application's start method is called. That way with every deployment you make you have the migrations just run and update the application automatically.

Check out this post from AppHarbor. <a href="http://blog.appharbor.com/2012/04/24/automatic-migrations-with-entity-framework-4-3" rel="nofollow">http://blog.appharbor.com/2012/04/24/automatic-migrations-with-entity-framework-4-3</a>

The gist is basically you want to enable auto migrations then call the DatabaseInitializer from your code, either from the OnModelCreating method or from your Global.asax.

blocks|key|1788163|text|您可以使用EF命令(update-database+-script)获取脚本，也可以手动编写脚本。这不是在生产环境中更新数据库的最重要的事情。对我来说，最重要的事情是确保所有脚本都正确运行，并且它们已经像预期的那样影响了记录。在我看来，您应该有一个生产前环境，数据库应该是生产环境的副本。这样，您就可以在非常相似的环境中运行脚本和部署应用程序，并查看是否存在任何问题。有时脚本在DEV环境中可以正确执行，但在生产环境中会失败。为了避免令人头疼的问题，您应该在预生产环境中模拟生产环境。关于脚本，如果团队有多个开发人员，我倾向于将脚本分为结构脚本和数据脚本。结构脚本改变数据库的结构(添加表、向表中添加列等)数据脚本插入/更新/删除记录。此外，每个脚本都应该指定它的依赖项，这样它们就不会以错误的顺序执行。在表A创建之前，无法执行表A中插入行的数据脚本。这就是我要做的：-Define一个用于注册已执行脚本的表。例如:+ExecutedScriptsHistory。-Each脚本有一个编号和一个名称。执行脚本时，会在表ExecutedScriptsHistory中插入一个新行。-Before脚本被执行时，它检查它的依赖关系。为此，它检查脚本是否已执行(存在于表ExecutedScriptsHistory中)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1788164|运行脚本后，您可以检查ExecutedScriptsHistory是否已执行了所有脚本。此策略类似于Microsoft在EF迁移中选择的策略，但您可以完全控制它。|1788165|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You can get the scripts using EF commands (update-database -script) or you can write the script manually. This is not the most important thing about updating the database in production environment. For me, the most important thing is to be sure that all the scripts were run correctly and they have affected records as expected. 
In my opinion, you should have a preproduction environment and the database should be a copy of the production environment. This way, you can run the scripts and deploy the application in a pretty similar environment and see if there are any problems. Sometimes the scripts are executed correctly in DEV environment but they fail in production environment. To avoid a headache, you should simulate the production environment in a preproduction environment.
Regarding the scripts, if the team has more than one developer I prefer to categorize the scripts in structure scripts and data scripts. Structure scripts alters the structure of the database (add a table, add a column to a table, etc.) and data scripts inserts/updates/deletes records. Also, each script should specify its dependencies so they cannot be executed in the wrong order. A data script that inserts rows in table A cannot be executed until table A has been created. This is what I do:
-Define a table for registering the executed scripts. For example: ExecutedScriptsHistory.
-Each script has a number and a name.
-After a script is executed, a new row is inserted in table ExecutedScriptsHistory.
-Before a script is executed, it checks its dependencies. In order to do that, it checks if the scripts have been executed (exists in table ExecutedScriptsHistory).

After you have run the scripts, you can check if all the scripts have been executed checking ExecutedScriptsHistory. This strategy is similar to the one chosen by Microsoft in EF Migration but you have full control of it.

blocks|key|1788337|text|只是为了给大家一个简单的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1788338|这是您的迁移文件夹Configuration.cs中的“更新数据库”：|1788339|++++internal+sealed+class+Configuration+:+DbMigrationsConfiguration<projectname.Models.dbContext>
{
++++public+Configuration()
++++{
++++++++AutomaticMigrationsEnabled+=+true;
++++++++AutomaticMigrationDataLossAllowed+=+true;+//+Update-Data+-Force+(deletes+columns+etc)
++++}|code-block|syntax|javascript|1788340|要在远程服务器上首先“启用迁移”，请将以下内容添加到您的Global.asax.cs文件：|1788341|++++++++protected+void+Application_Start()
++++{
++++++++....
++++++++System.Data.Entity.Database.SetInitializer(new+MigrateDatabaseToLatestVersion<dbContext,+Migrations.Configuration>());|1788342|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

just to give everyone the simple answer.

This is the "Update-Database"
In your Migrations folder, Configuration.cs:

<pre><code> internal sealed class Configuration : DbMigrationsConfiguration&lt;projectname.Models.dbContext&gt;
{
 public Configuration()
 {
 AutomaticMigrationsEnabled = true;
 AutomaticMigrationDataLossAllowed = true; // Update-Data -Force (deletes columns etc)
 }
</code></pre>

And to "Enable migrations" in the first place on a remote server, add this to your Global.asax.cs file:

<pre><code> protected void Application_Start()
 {
 ....
 System.Data.Entity.Database.SetInitializer(new MigrateDatabaseToLatestVersion&lt;dbContext, Migrations.Configuration&gt;());
</code></pre>

I can use package manager to run 'update-database -verbose' locally.

Probably a stupid question but I can't find it online - once my website is deployed - how can I run this manually on the server?

Secondarily - what other strategies would you recommend for deploying database migrations to production - and how would they be preferable?

Thanks

ASP.NET MVC 4, Migrations - How to run 'update-database' on a production server

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我可以使用包管理器在本地运行'update-database -verbose‘。这可能是一个愚蠢的问题，但我在网上找不到它--一旦我的网站部署好了--我如何在服务器上手动运行它？其次，对于将数据库迁移部署到生产环境，您还会推荐哪些其他策略?这些策略在哪些方面更可取？谢谢

问更新MVC4，迁移-如何在生产服务器上运行‘ASP.NET -database’
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问更新MVC4，迁移-如何在生产服务器上运行‘ASP.NET -database’EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问更新MVC4，迁移-如何在生产服务器上运行‘ASP.NET -database’
EN