Database migrations are a great way to regain control of this mess.
数据库迁移是一个很好的方式去处理这些混乱的情况。
LiquiBase: Download LiquiBase to begin performing automated database migrations.
LiquiBase：下载LiquiBase，开始执行自动化的数据库迁移。
While SQL Server 2005 is not exactly new, database migrations can take months or even years of planning.
虽说SQLServer 2005不完全算全新的产品，但是数据库迁移要花几个月甚至几年的时间。
Rake is Ruby's build tool that is used to automate shell-like commands, such as packaging and deploying Ruby code, and performing database migrations.
Rake是Ruby的构建工具，用于自动执行类似于shell的命令，如打包和部署Ruby代码以及执行数据库迁移。
If your migrations are correct, each migration leaves your database in a consistent state, with no manual intervention.
如果迁移正确，那么每个迁移都会把数据库置于一个一致的状态，不需要手工干预。
Some migrations change more than one column to consolidate a single logical change in a database.
有些迁移修改不只一个列，形成数据库中单一的逻辑变化。
In addition to structural changes to the database, migrations can include SQL commands for manipulating data.
除了能够对数据库结构做出变更之外，迁移操作中还可以包括用于操作数据的SQL命令。
Migrations from Oracle to the DB2 9.5 LUW in compatibility mode allow one-to-one mapping of source database syntax to target database syntax.
以兼容性模式从Oracle迁移到DB 2 9.5LUW，这允许从源数据库语法到目标数据库语法进行一对一映射。
To use migrations, you only need a Rails project and a database.
要使用迁移，只需要一个Rails项目和一个数据库。
As a DB2 UDB consultant, Raul helped IBM business partners with migrations from other relational database management systems to DB2, and with database performance and application design issues.
作为一名DB 2udb顾问，Raul曾帮助IBM业务伙伴从其他关系数据库管理系统迁移到DB2，并帮助他们解决数据库性能和应用程序设计问题。
This article takes a deeper look at Ruby on Rails migrations — Rails's solution for dealing with changes to a production database.
这篇文章深入研究了RubyonRails迁移——Rails处理生产数据库变化的解决方案。
Because you are copying the database over, you do not have to apply your Rails migrations first.
由于您正在复制数据库，因此您不必先应用您的Rails迁移。
If you want to start using migrations with an existing database, you can snapshot your existing schema with rake schema_dump.
如果想对现有数据库使用迁移，可以用rake schema_dump对现在的模式做个快照。
Prior to the seed file, no convention existed for initialization, and many developers put code in migrations, clouding the differentiation between creating the database and populating it.
在Seed文件之前，不存在初始化的惯例，许多开发人员把代码放入迁移中，这样容易混淆创建数据库和填充数据库之间的不同之处。
How can I use Entity Framework to use an existing database, and how can I use migrations to switch between DB versions?
我如何使用实体框架使用一个现有的数据库，以及如何使用迁移数据库版本之间切换？
How to avoid migrations in model first database with Entity Framework 5 and code first entities?
如何避免迁移模型首先数据库实体框架5和代码第一实体吗？
How to avoid migrations in model first database with Entity Framework 5 and code first entities?
如何避免迁移模型首先数据库实体框架5和代码第一实体吗？
应用推荐