2

We use VSTS Database Edition to version control our database schemas. I like the idea of how it is supposed to work but have a big issue with the Schema Comparison feature. I like to use it for my deployments to see what has changed in the project vs a target database. Unfortunately, it shows many changes for objects that have not been changed. That happens even if I do it immidiately after re-creating a db project from the database.

The differences it finds are mostly white space. Some are caused by a different representation of the same thing, for example default constraints, "DEFAULT ((0))" vs "DEFAULT (0)". While I can go ahead and deploy the changes anyway and it does not cause any problems, it is definitely not ideal because it is hard to find actual changes when at least 50% of all objects are shown as modified. Is there any way to make this work better?

4

2 回答 2

3

我一直希望 VSTS 数据库版会变得更加可靠。同时，我仍然信任并使用redgate 的 SQL 比较来区分数据库。你可以告诉它你希望它如何处理空白、评论等。

我使用 SQL Compare 大约 5 年了，它一直非常可靠。我有自动构建脚本，使用 SQL 比较引擎 API 来区分我们的生产和开发数据库并自动生成更改脚本。

PS。我不隶属于redgate。我只是根据我的经验陈述我的看法。此外，为小家伙生根也没有错。

于 2009-06-17T15:54:21.813 回答
3

对此的解决方案是升级到 Database Edition GDR R2 版本，这是 Mitch Wheat 在他的评论中提出的建议。我之前用的是VS2008自带的标准版。GDR 版本似乎有一些很好的可用性特性，它解决了我在模式比较方面的所有问题。

有关 VSTS 数据库版 GDR 的一般信息：http: //msdn.microsoft.com/en-us/magazine/dd483214.aspx。

最新版本下载在这里。

于 2009-06-17T16:04:43.950 回答