Managing SQL Stored Procedures’ Version

serversqlsvnversion controlversioning

I am working with a team of 5 persons. We are using SQL Server as our database.
Since long time I want to store the Stored Procedures in SVN so that the versions can be maintained. Is there any tool which can be used as a plugin with SQL Server Management Studio and allows checkin from there.

Best Answer

Sounds like Red Gate's SQL Source Control might be what you're looking for.

It says it connects to "TFS, SVN, SourceGear Vault, Vault Pro, Mercurial, Perforce, Git, and any source control system with a capable command line," and that it "links your databases to your existing source control system straight from SSMS".

I haven't used it personally, but I have used other Red Gate SQL tools, and they have been excellent.

Related Solutions

Version Control – Creating a Version Control Strategy for SVN

If you want a unified build process, then be sure to put branches/tags/trunk at the root, like this:

branches/
tags/
trunk/
  dev/
    ...

If you don't need a unified build process, then you can put branches/tags/trunks within each project if you want. However, it might be difficult to migrate to a unified build after having put them within each project. A unified build has advantages, such as eliminating the need to publish shared components among projects -- they're all part of the build.

Personally, I like a unified build process. Furthermore, I don't think you should have a "dev" project. You should have projects directly under trunk, and then branch trunk into a dev branch. Use tags for releases. For example, I would do it like this:

branches/
  dev/
    Site1/
    Site2/
    WebService/
    SharedCode/
tags/
  release1/
    Site1/
    Site2/
    WebService/
    SharedCode/
trunk/
  Site1/
  Site2/
  WebService/
  SharedCode/

SQL Server Version Control – Best Practices

Technically you don't even need a tool, you can script the objects directly and check them into source control. It is a bit more work without the tool, but it is definitely workable.

BTW: I've used the RedGate tool and it is pretty slick and worth the money.

Best Answer

Related Solutions

Version Control – Creating a Version Control Strategy for SVN

SQL Server Version Control – Best Practices

Related Topic