On Thu, Jun 10, 2010 at 3:34 PM, Paul Duran <[email protected]>wrote:
> I used Tarantino for database change management on a previous project: > http://code.google.com/p/tarantino/wiki/DatabaseChangeManagement . It > worked pretty well in general but i prefer the idea of separating schema > changes, data changes and stored procedure changes. We don't have > redgate so when making changes in SqlServer, i generally just click the > 'create script' button. > Took a quick look at that. Seems a little odd; the "ideal environment" implies that you wouldn't even need the tool! But nevertheless, if you used it I suppose it was good for something. Anyway, I think the consenus is that there is a theoretical solution known by all, and the application of that is where it gets difficult. For me, I'm happy with a plan of sorts that I have, and one day it's probably worth considering the underlying "problem" and if a different type of database is more appropriate (i.e. CouchDB and friends: http://couchdb.apache.org/). > Cheers, > Paul. > -- silky http://www.programmingbranch.com/
