Geek Answers Handbook

Version control system for a small group of database developers

I am responsible for a small development team, and we are mainly engaged in the development of the database. We currently use MS Visual Source Safe as our version control system, but it has its own limitations and we are seriously thinking about a change. Which system would you choose?

+6
git version-control svn sourcegear-vault
source share
11 answers

Look at the use of SVN, from personal experience I will stay far from ClearCase.

At my company, we recently started using a control source to track database changes in a schema and stored procedures. This has greatly helped us in SVN to track changes. Its a shame, although the previous 4 years of work have been lost, because so far nothing about the database has been under the control of any control.

+4
source share

For a small team, SVN is better in my experience (I used CVS, SVN, and VSS in the past).

It is powerful, has a large user base and good tools such as web interfaces, etc.

Some people are likely to recommend git, but I think this is too much for what you are describing.

+11
source share

Our team uses Sourcegear Vault , which is very similar to CVS or VSS, just without some wrinkles.

+5
source share

Our team (.NET) switched to Subversion / TortoiseSVN , VisualSVN (for VisualStudio integration) and Trac a few months ago. I can not recommend these tools enough.

+4
source share

I would stay away from centralized, distributed version control systems give much more flexibility, while maintaining a centralized way of working.

For more technical experts, git might be fine; it was developed by the Linux kernel people after all.

Bazaar or mercurial is probably best for those looking for usability.

+3
source share

Subversion, find Visual SVN , it's free and easy to use.

You can also take a look at SQL Server Database Versioning with Subversion (SVN)

+1
source share

captivity.

Commercial software, and it's not free, like SVN, but it's great. Cross-platform, easy to use, graphical interfaces, command lines, etc.

+1
source share

In particular, for database development, and in case you use MS SQL, I would recommend that you take a look at Red Gate SQL Source Control , which can work through SVN / TFS / VSS / Vault and helps version control databases.

+1
source share

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

Works with branches that are great for parallel development ("branch to task template"). For each task (ticket, error, problem, whatever) you make a child branch. Plastic will update your "workspace" on the disk, so all files have the correct version. You can make as many changes and checks as you want, because you are working in your own branch, so no one will worry anymore if you check something that does not compile! It works LOVELY!

If you switch to another branch (because you have to make a quick fix), all changes are “pending” on the server, the current workspace is automatically updated to this other branch, you can make some changes + checkin, switch to your branch, over which you worked, and all files are deleted again, so that you can continue to work where you were before. Very nice.

He has a very cool GUI client, and it works on MacOS + Linux.

0
source share

I believe that SVN + SQL Examiner Suite is the best solution for keeping your database under version control .

0
source share

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

Configure it on a decent virtualization machine - one TFS vm, one SQL, one (possibly) build (only).

  • Source control when working with SQL Server.

  • Integrated Work Item Tracking

  • Can integrate continuous integration with testing, etc.

  • You can integrate sharepoint for documents.

Easy to configure in version 2010;)

0
source share

More articles:


All Articles