问题
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?
回答1:
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.
回答2:
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.
回答3:
Our team uses Sourcegear's Vault, which is a lot like CVS or VSS, just without some of the wrinkles.
回答4:
Our team (.NET) a few months ago switched to Subversion / TortoiseSVN, VisualSVN (for VisualStudio integration) and Trac. I can't recommend these tools enough.
回答5:
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.
回答6:
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)
回答7:
Perforce.
Commercial software, and it's not free like SVN, but it's great. Crossplatform, easy to use, GUIs, command lines, etc.
回答8:
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.
回答9:
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.
回答10:
I believe that SVN + SQL Examiner Suite is best solution for keeping your database under version control.
回答11:
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 ;)
来源：https://stackoverflow.com/questions/216834/source-control-system-for-small-database-dev-team