使用 MS Team System 2008 数据库版
我想开始对我们的数据库进行源代码控制。我在这里阅读了很多问题，发现 MS Team System 2008 with Database Edition 正是我所需要的。所以我们明白了，但我们确实有点迷失了。
首先，我们希望比较我们拥有的不同数据库（DEV、STA 和 PROD），因为我们从未对数据库进行过任何源代码控制，它们可能存在一些我们想要解决的差异。我读到 MS Team System 2008 DB Edition 可以做到这一点，但我认为我们还没有找到如何做到这一点。
一旦我们让每个数据库都处于相同的“状态”，我们就想创建某种计划，将本地开发人员数据库的更改传播到某些源代码控制（我认为将数据库项目放在 SVN 下就可以完成这项工作）。然后有办法生成“更改脚本”以将更改传播到 STA，当然然后再传播到 PROD。关于如何做到这一点有什么想法吗？
这可能已经被问过，但我想我没有找到任何东西，因为我没有使用正确的术语进行搜索。
非常欢迎指向另一个 SO 问题或一些描述如何使用 MS Team System 2008 数据库版本和 SQL Server 2005 项目的文章的链接。
感谢大家的
欢呼
I'm wanting to start source controlling our DBs. I've read a lot of questions here and have found that MS Team System 2008 with Database Edition is what I need. So we get it and we are kind of lost really.
We would like in first place, compare the different DBs we have (DEV, STA and PROD) because we had never done any source control on the DBs, they probably have some differences we would like to solve. I've read that MS Team System 2008 DB Edition could do it, but I think we are not finding how to.
Once we had every DB on the same "state", we would like to create some kind of plan to spread changes from local developers DB to some source control (I think putting the Database Project under SVN will do the job). And then have a way to generate the "change script" to propagate the changes to STA, and then to PROD of course. Any ideas of how to do this?
This probably has been already asked, but I guess I'm not finding anything because I'm not using the correct terms to search.
A link to another SO question or to some article describing how to work with MS Team System 2008 Database Edition and SQL Server 2005 projects will be very welcomed.
Thanks to all
Cheers
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
第一个问题的答案是 Visual Studio Team System - 数据库开发人员的架构和数据比较功能。您应该在“构建”和“测试”之间有一个名为“数据”的菜单项。在该数据菜单下有“架构比较”和“数据比较”等选项 - 它们使用起来相当直观。
下一个问题是如何在数据库上使用源代码控制。源代码控制应该是模式的真实来源之一。当您创建数据库项目并将它们存储在源代码管理中时，我建议首先让它们镜像生产。然后，您可以将更改应用于项目，并将项目与目标环境（如开发/QA/产品）进行比较，以识别和编写可以移至这些环境的差异。
编辑：
我还强烈推荐书中的第8章“专业团队”基础服务器”。该章介绍了如何使用 Team Edition for Database Professionals 来管理架构。
The answer to your first question is the schema and data comparison features of Visual Studio Team System - Database Developer. You should have a menu item between Build and Test called Data. Under that data menu are options like "Schema Compare" and "Data Compare" - they are fairly intuitive to use.
The next question is how to use the source control on the databases. Source control should be your one source of truth for schema. When you create your database projects and store them in source control, I would suggest having them mirror production initially. Then you can apply changes to the projects and compare the projects to target environments like dev/QA/prod to identify and script out differences that could be moved to those environments.
EDIT:
I would also highly recommend chapter 8 in the book "Professional Team Foundation Server". That chapter covers usage of Team Edition for Database Professionals for the purposes of managing schemas.