{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 走好不送 的问题《Source control system for small database dev team》','https://www.manongdao.com/q-241322.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am responsible for a small development team and we deal mainly with database development. We are currently using MS Visual Source Safe as our source control system, but it has its limitations and we are seriously thinking about changing. What system would you choose?
相关问题
- Why does recursive submodule update from github fa
- Extended message for commit via Visual Studio Code
- How can I set the SVN password with Emacs 23.1 bui
- Emacs shell: save commit message
- Can I organize Git submodules in a flat hierarchy?
相关文章
- 请教Git如何克隆本地库?
- What is the tortoisehg gui equivalent of doing “hg
- How to use Mercurial from Visual Studio 2010?
- GitHub:Enterprise post-receive hook
- Git Clone Fails: Server Certificate Verification F
- SSIS solution on GIT?
- Is it possible to do a “destroy history” in TFS?
- Is there a version control system abstraction for
Subversion, look for Visual SVN , it free and real easy to use.
You might also take a look at SQL Server database versioning with Subversion (SVN)
I'd stay away from the centralized ones, distributed version control systems give much more flexibility, while still allowing centralized way of working.
For more technical people git could be good, it has been developed by Linux kernel people after all.
Bazaar or mercurial are probably better for those looking for ease of use.
Specifically for a database development and just in case you are using MS SQL, I would recommend you to take a look at Red Gate's SQL Source Control product, which can work over SVN/TFS/VSS/Vault and helps to source control databases.
For a small team, SVN is best, in my experience (I've used CVS, SVN, and VSS in the past).
It's powerful, has a large userbase, and good tools like web interfaces, etc.
Some folks will probably recommend git, but I think it's overkill for what you describe.
Our team (.NET) a few months ago switched to Subversion / TortoiseSVN, VisualSVN (for VisualStudio integration) and Trac. I can't recommend these tools enough.
I believe that SVN + SQL Examiner Suite is best solution for keeping your database under version control.