Source code control – SQL Server and Oracle

One of the things that I find very poorly done in most SQL Server sites that I visit is source code control for database objects.

You can connect SQL Server Management Studio with source code control systems, to make it easier to manage scripts, etc. One way of doing this is to configure an SCCI (source code control interface) provider. You can get the one that works with SSMS here:

Once you've installed that, you'll find an "Add to source control" option appearing when you create new script projects. If it doesn't seem to be enabled, see this article:

You'll also need a TFS (Team Foundation Services) server or an SVN server. A really good option now is the TFS Online offering which is also free for up to 5 users: 

Another option to consider, particularly if you work with other database engines as well are the 3rd party tools. I've previously mentioned the Red-Gate source code control tools. You'll find info on them here:

A key advantage of these is that they are pretty easy to use and work with a wider variety of source code control engines. As well as TFS and SVN, they work with Git, Mercurial, Vault, Perforce and others.

Today they have announced updated support for Oracle:

It works with SVN and TFS.

Either way, there are lots of offerings out there now. It's important that you start to investigate one of them if you haven't already done so.

4 thoughts on “Source code control – SQL Server and Oracle”

  1. There's also SSDT 2012 in the most uptodate version from March 2013 i think. Seems to work nicely, though as an add-in from within visual studio 2012, but you can use the visual studio 2012 shell as basis to install SSDT 2012 on.

Leave a Reply

Your email address will not be published. Required fields are marked *