我通过保存创建/更新脚本和生成sampledata的脚本来完成。

Kira的主要用例之一是通过显式地将数据库外部的模式指定为代码来进行数据库升级。然后，它可以管理数据库，并将其从任何版本升级到任何版本。

数据库本身?没有

创建它们的脚本，包括静态数据插入、存储过程等;当然可以。它们是文本文件，它们包含在项目中，像其他东西一样签入和签出。

当然，在理想情况下，您的数据库管理工具可以做到这一点;但你必须遵守纪律。

“简短版本:将您的生产数据库转储到git存储库中，以实现即时备份解决方案。”

A big problem, often overlooked, is that for larger web based systems, it is required to have a transitional period or bucket testing approach to making new releases. This makes it essential to have both rollback and a mechanism for supporting both the old and new schema in the same DB. This requires a scaffolding approach (made populist by the Agile DB folks). In this scenario, lack of process in DB source control can be a total disaster. You need old schema scripts, new schema scripts and a set of intermediate scripts, as well as a tidy up, once the system is fully on the new version (or rolled back).

需要的不是从头开始重新创建模式的脚本，而是一种基于状态的方法，在这种方法中，您只需要脚本将DB从一个版本移动到另一个版本，向前或向后移动到所需的状态。您的DB变成了一系列状态脚本，可以轻松地对其进行源代码控制，并与源代码的其余部分一起标记。

作为一种规则，我们将所有的对象代码(存储过程、视图、触发器、函数等)都保存在源代码控制中，因为这些对象都是代码，而且几乎所有其他答案都同意，代码属于某种形式的版本控制系统。

As for CREATE, DROP, ALTER statements, etc. (DDL), we developed and use BuildMaster to manage the deployment of these scripts such that they can be run once and only once against a target database (whether they fail or not). The general idea is that developers will upload change scripts into the system and when it comes time for deployment, only the change scripts that haven't been run against the target environment's database will be run (this is managed very similarly to Autocracy's answer). The reason for this separation of script types lies in that once you manipulate a table's structure, add an index, etc., you effectively cannot undo that without writing a brand new script, or restoring the database - as opposed to the object code where you can simply drop a view or stored procedure then recreate it.

例如，当您将生产数据库恢复到集成环境中时，可以看到一些好处，系统会自动准确地知道哪些脚本没有运行，并将更改新恢复的数据库的表结构，使其与开发相关。