本文介绍了共享开发数据库或私有开发人员数据库?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Hello All,

Hello All,

您使用其中一个与另一个有什么争论?我们传统上使用共享开发数据库作为"不断发展的事实来源",但最近一直在尝试VS2010中的数据库项目以及私有开发人员数据库,作为
实现数据库版本控制的一种方式。问题是,它非常麻烦,而且还没有人看到ROI。 

What are your arguments for using one vs the other? We have traditionally used a shared development database as the 'evolving source of truth' but have recently been trying out database projects in VS2010 along with private developer databases as a way to achieve version control for our database. The problem is, it's been very cumbersome and no one is seeing the ROI yet. 

例如,如果dev在其私有数据库中创建了一个新表,则向其添加查找值然后,他必须将这些更改编写回源代码控制脚本,并添加脚本来创建这些查找值。每当他最近获得
时,他必须做相反的事情。每次他打开一个分支或者我们被搞砸时,他必须记住这样做。此外,架构比较工具并没有让我们高度自信。 

For example, if a dev creates a new table in his private DB, adds lookup values to it, he then has to script those changes back into source control as well as add a script to create those lookup values. He has to do the opposite of that everytime he gets latest. And he has to remember to do that each time he opens a branch or we're screwed. In addition, the schema comparison tools haven't left us with a high degree of confidence. 

我的问题是,大多数人使用哪种方法以及为什么?

My question is, which method are most people using and why?

推荐答案

最好的问候,


这篇关于共享开发数据库或私有开发人员数据库?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-02 18:45
查看更多