VSTS 数据库版本架构比较
我们使用 VSTS Database Edition 来对数据库架构进行版本控制。 我喜欢它的工作原理，但对架构比较功能有一个大问题。 我喜欢在部署中使用它来查看项目与目标数据库中发生的变化。 不幸的是，它显示了许多尚未更改的对象的更改。 即使我在从数据库重新创建数据库项目后立即执行此操作，也会发生这种情况。
它发现的差异主要是空白。 有些是由同一事物的不同表示引起的，例如默认约束“DEFAULT ((0))”与“DEFAULT (0)”。 虽然我可以继续部署更改，并且不会造成任何问题，但这绝对不理想，因为当所有对象的至少 50% 显示为已修改时，很难找到实际更改。 有什么办法可以让这项工作变得更好吗？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
解决方案是升级到数据库版 GDR R2 版本，这是 Mitch Wheat 在他的评论中建议的。 我之前用的是VS2008自带的标准版。 GDR 版本似乎有一些很好的可用性功能，它解决了我在架构比较方面的所有问题。
有关 VSTS 数据库版本 GDR 的一般信息：http://msdn.microsoft.com/ en-us/magazine/dd483214.aspx。
最新版本下载位于此处< /a>.
The solution to this was upgrading to the Database Edition GDR R2 release, which was suggested by Mitch Wheat in his comment. I was using the standard version that came with VS2008 before. GDR release appears to have some nice usability features and it fixed all my problems with the Schema Comparison.
General info on VSTS Database Edition GDR: http://msdn.microsoft.com/en-us/magazine/dd483214.aspx.
Latest version download is here.
我一直希望 VSTS 数据库版本能够变得更加可靠。 与此同时，我仍然信任并使用redgate的SQL Compare来比较数据库。 您可以告诉它您希望它如何在非常精细的级别上处理空白、注释等。
我使用 SQL Compare 大约有 5 年了，它一直非常可靠。 我有自动构建脚本，使用 SQL Compare 引擎 API 来区分我们的生产和开发数据库并自动生成更改脚本。
附言。 我不隶属于瑞德盖特。 我只是根据我的经验发表我的看法。 此外，支持这个小家伙也没有什么错。
I keep hoping VSTS Database Edition will get more reliable. In the meantime, I still trust and use redgate's SQL Compare to diff databases. You can tell it how you want it to treat white space, comments, etc. on a very granular level.
I have been using SQL Compare around 5 years and it has always been very reliable. I have automated build scripts that use the SQL Compare engine APIs to diff our production and dev database and generate change scripts automatically.
PS. I am not affiliated with redgate. I am just stating my opinion based on my experience. Also, there is nothing wrong with rooting for the little guy.