Visual Studio Team System 数据库版 (GDR) 的真正优势是什么? [英] What are the real benefits of Visual Studio Team System Database Edition (GDR)?
问题描述
是否有兴趣广泛使用 VSTS 数据库版，如果是，您认为与标准 Visual Studio 数据库项目相比哪些功能最有用?
Interested if anyone has used VSTS Database Edition extensively and, if so, which features did you find the most useful over the standard Visual Studio database projects?
与 RedGate 的 SqlCompare 等替代模式管理选项或工具相比，最引人注目的功能是什么?
What are the most compelling features as opposed to alternative schema management options or tools like RedGate's SqlCompare etc?
编辑:Microsoft 刚刚发布了RTM 版本的数据库版 (GDR)，它增加了对 SQL Server 2008 的支持 - 链接是 此处.我之前曾在这里写过(简要).
Edit: Microsoft just released the RTM version of Database Edition (GDR) which adds support for SQL Server 2008 - link is here. I've previously blogged (briefly) about it here.
有没有人有机会在东德做任何真正的工作?看起来有一些真正的增强功能，包括重构支持.我真的很想知道人们是否在 SQL Server 2008 中使用它...
Has anyone had a chance to do any real work with the GDR? It looks like there are some real enhancements including refactoring support. I'd be really interested to hear if people are using it with SQL Server 2008...
推荐答案
我们在 Stack Overflow 上使用 Team Suite 的数据库版本功能.正如 Vaibhav 所说，大多数情况下它很有用，因为它为您提供了一种将数据库逆向工程到源代码控制的一键式方法，并使其保持最新状态.
We use the database edition functionality of Team Suite on Stack Overflow. As Vaibhav said, mostly it is useful because it gives you a one-click way to reverse engineer a database into source control, and keep it up to date.
请注意，它还具有不错的数据和架构比较工具.您可以将项目与物理数据库进行比较，反之亦然.无论您在何处进行更改，无论是在文件系统数据库项目中，还是在物理数据库本身中，这都可以让您的数据库保持最新状态变得非常容易.
Note that it also has decent Data and Schema compare tools as well. You can compare projects to physical databases and vice-versa. This makes it pretty easy to keep your database up to date, no matter where you make changes -- in the filesystem database project, or in the physical database itself.
这篇关于Visual Studio Team System 数据库版 (GDR) 的真正优势是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
