The Tarantino Project - automated database migrations and more

 

The Tarantino project is a collection of libraries and tools to facilitate change management and development

 

The Tarantino project contains a number of useful components for:

Tarantino is currently being developed and extended.  If you would like to contribute, the most welcome patch would be Oracle support for the database migrations.  Currenlty, only SQL Server is supported.


Trackbacks

Reflective Perspective - Chris Alcock » The Morning Brew #161 Posted on 8.19.2008 at 3:08 AM

Pingback from Reflective Perspective - Chris Alcock » The Morning Brew #161

Dew Drop - August 19, 2008 | Alvin Ashcraft's Morning Dew Posted on 8.19.2008 at 8:08 AM

Pingback from Dew Drop - August 19, 2008 | Alvin Ashcraft's Morning Dew

Comments

Ash Tewari said on 8.18.2008 at 3:49 PM

A command-line tool to implement an incremental database version update strategy is also available here : www.tewari.info/.../dbupdater

Parag Mehta said on 8.18.2008 at 11:32 PM

Hi Jeff,

I am looking at it, however it's not a good name. Reminds me of "Quentin Tarantino" who made nothing but horror films :)

Krzysztof Ko┼║mic said on 8.19.2008 at 1:04 AM

How much is it dependent on NAnt? Is there some MsBuild support comming?

Jeffrey Palermo said on 8.19.2008 at 6:56 AM

@Krzysztof,

It is very much coupled to NAnt. There is not MSBuild support planned, but if you'd like to contribute that patch, I'm sure it would only be a single C# class to write.

Eric Hexter said on 8.19.2008 at 10:21 PM

@Krzysztof - the msbuild implementation would be trivial to implement.

This is the only file that references Nant for the migration project

tarantino.googlecode.com/.../ManageSqlDataba

As you will see there is only a single line that is used to call into the migration code,

manager.Upgrade(ScriptDirectory.FullName, Server, Database, IntegratedAuthentication, Username, Password, Action, this);

The rest is code to manage Nants requirements for passing data to the task.

Serfmum Yossarian said on 8.20.2008 at 10:50 AM

How do you deal with branching and merging? We use a similar database change management strategy using private dev databases, incremental change scripts and continuous integration. However, branching and merging has always been one of those things that ends up being a real pain. Any insights?