Source control system for small database dev team

2019-01-27 23:41发布

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?

11条回答
何必那么认真
2楼-- · 2019-01-28 00:04

TFS 2010 - you should have the right to use it for 5 people, otherwise ther are various cheap offers for companies.

Set it up on a decent computer with virtualization - one vm TFS, one SQL, one (possibly) build (only).

  • Source control with SQL Server behing.

  • Integrated work item tracking

  • Can integrate continuous integration with testing etc.

  • Can integrate sharepoint for documents.

Easy to set up in the 2010 version ;)

查看更多
做自己的国王
3楼-- · 2019-01-28 00:06

Look into using SVN, from personal experience I would stay far far away from ClearCase.

At my company we recently started using source control to track database changes in schema and stored procs. It has helped tremendously that we have it all under SVN to track the changes. Its a shame though that the previous 4 years worth of work has been lost because before now nothing about the DB was under any sort of revision control.

查看更多
对你真心纯属浪费
4楼-- · 2019-01-28 00:09

Perforce.

Commercial software, and it's not free like SVN, but it's great. Crossplatform, easy to use, GUIs, command lines, etc.

查看更多
淡お忘
5楼-- · 2019-01-28 00:11

Our team uses Sourcegear's Vault, which is a lot like CVS or VSS, just without some of the wrinkles.

查看更多
一夜七次
6楼-- · 2019-01-28 00:12

Not free, but a very nice (!) system is "PlasticSCM": http://www.plasticscm.com/demos/plastic28/index.html

Works with branches, which works very good for parallel development ("branch per task pattern"). For every task (ticket, bug, issue, whatever) you make a child branch. Plastic will update your "workspace" on disk, so all files have the right version. You can make as much changes and checkins as you want, because you work in your own branch, so nobody else get troubles if you checkin something that does not compile! This works LOVELY!

If you switch to another branch (because you must make a quick bugfix), all changes are "shelved" on the server, current workspace is automatically updated to that other branch, you can make some changes + checkin, switch back to your branch you were working on, and all files are unshelved again, so you can continue where you were before. Very very nice.

It has a very cool GUI client, works also on MacOS + Linux.

查看更多
登录 后发表回答