RedGate软件提供了一些很棒的工具，可以帮助你对数据库进行版本化。确保让开发者为开发工作构建自己的独立本地数据库，而不是依赖于“开发服务器”，因为“开发服务器”有时可能停机，有时也可能不停机。

我对创建脚本进行了版本控制，并在其中使用了svn版本标记。然后，每当我得到一个将要使用的版本时，我就在dbpatches/目录中创建一个脚本，命名为要上卷到的版本。该脚本的任务是在不破坏数据的情况下修改当前数据库。例如，Dbpatches /可能有名为201、220和240的文件。如果数据库当前处于201级别，则应用补丁220，然后再应用补丁240。

DROP TABLE IF EXISTS `meta`;
CREATE TABLE `meta` (
  `property` varchar(255),
  `value` varchar(255),
  PRIMARY KEY (`property`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
INSERT INTO `meta` VALUES ('version', '$Rev: 240 $');

在考虑一个好的补丁之前，不要忘记测试你的代码。购者自慎!

我有一切必要的重新创建我的数据库从裸露的金属，减去数据本身。我相信有很多方法可以做到这一点，但我所有的脚本等都存储在subversion中，我们可以通过将所有这些从subversion中取出并运行安装程序来重建DB结构等。

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重新初始化到当前版本。

我们对所有dabase创建的对象进行源代码控制。为了让开发人员保持诚实(因为你可以在没有源代码控制的情况下创建对象)，我们的dba定期寻找不在源代码控制中的任何东西，如果他们找到了什么，他们就会丢弃它，而不询问它是否ok。

必须阅读将数据库置于版本控制之下。查看K. Scott Allen的系列帖子。

When it comes to version control, the database is often a second or even third-class citizen. From what I've seen, teams that would never think of writing code without version control in a million years-- and rightly so-- can somehow be completely oblivious to the need for version control around the critical databases their applications rely on. I don't know how you can call yourself a software engineer and maintain a straight face when your database isn't under exactly the same rigorous level of source control as the rest of your code. Don't let this happen to you. Get your database under version control.