SQL Source Control 3.0

Case study from Peter Duncanson

SQL Source Control and Kiln

I'm the managing director at Offroadcode, a small code shop specializing in building clever websites for our clients. I'm the one in the office who likes to find and play with new kit before rolling it out to the other guys – if it passes the test.

I had looked at SQL Source Control when it was in Beta, but it only worked with SVN then. We had just made the jump to Kiln, and I didn't want to go back, but I knew SQL Source Control was a good enough product that it would only be a matter of time before Red Gate ported it to work with Kiln, and here it is.

To have our databases inside Kiln is a perfect match for us. We keep all our build scripts, source code, and so on in Kiln, but the database has always been one of those "dark" areas. We never quite came up with a solution for how best to manage creating, recreating, and changing it. I've already added three of our databases into Kiln using SQL Source Control. From the moment you get that first one entered, the value is so obvious that you just have to add others.