Duncan Pryde (3/10/2011)
Thanks for the links - I discovered after I posted that you have a number of entries on your blog as well which look interesting.
I think what I'm after is some idea as to why I should start using "Datadude" if I've never used it before. I'll have a look through the various articles and see what I can find though.
yeah, that's a hard one to articulate. For me, I reached a point where it just "clicked" and I don't think that can happen until you use the product.
The big benefits as far as I can see them are:
-Development-time error checking (i.e. find out about errors before you actually run the code - so you wont get caught by deferred name resolution)
-Declarative development. (i.e. You define what the database state should be and the tool works out how to get it to that state, as opposed to you having to author all of the ALTER statements)
-Code analysis (i.e. it highlights bad coding practices)