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

查看使用源代码控制管理数据库更改的LiquiBase。

My team versions our database schema as C# classes with the rest of our code. We have a homegrown C# program (<500 lines of code) that reflects the classes and creates SQL commands to build, drop and update the database. After creating the database we run sqlmetal to generate a linq mapping, which is then compiled in another project that is used to generate test data. The whole things works really well because data access is checked at compile time. We like it because the schema is stored in a .cs file which is easy to track compare in trac/svn.

The most successful scheme I've ever used on a project has combined backups and differential SQL files. Basically we would take a backup of our db after every release and do an SQL dump so that we could create a blank schema from scratch if we needed to as well. Then anytime you needed to make a change to the DB you would add an alter scrip to the sql directory under version control. We would always prefix a sequence number or date to the file name so the first change would be something like 01_add_created_on_column.sql, and the next script would be 02_added_customers_index. Our CI machine would check for these and run them sequentially on a fresh copy of the db that had been restored from the backup.

我们还准备了一些脚本，开发人员可以用一个命令将本地db重新初始化到当前版本。

是的，当然。每当有更改时，我们生成PostgreSQL模式的转储并签入。它已经救了我们很多次，而我才上任几个月。

我已经使用RedGate SQL Compare Pro与脚本文件夹进行模式同步，然后我将所有更新提交给版本控制。效果很好。