Source control system for small database dev team [closed]

Question

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?

Answer 1

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.

Answer 2

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

Answer 3

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.