We had this working beautifully in this way at a place I worked in the UK. DB changes where automagically red-gated to the source system, and added to the auto build, deploy and test.
On 10 June 2010 14:09, silky <[email protected]> wrote: > On Thu, Jun 10, 2010 at 12:07 PM, mike smith <[email protected]> wrote: > > On 10 June 2010 12:00, silky <[email protected]> wrote: > > > I know there was a thread on this recently. The versioning inside the > > > DB is obviously one component of this, but scripting the changes is > > > the other part. > > > > > > Does anyone automate the scripting? It seems to me that it would be > > > cool if you had a command-line tool that scripted the latest changes > > > to local DB that you were working with (i.e. configurable in some > > > script) and then saved those changes to a file as part of a > > > source-control commit operation. That is to say, you'd script this > > > tool as a pre-commit operation (locally, I think most source control > > > systems support this kind of operation). > > > > > > I'm pretty sure someone on this list has such a tool. I can't quite > remember. > > > > > > Anyone taking this approach? Is it a good idea? > > > > > > Something like Redgate? > > > > http://www.red-gate.com/products/SQL_Compare/index.htm > > Yes, I've used RedGate, I'm more talking about the approach in general. > > > > -- > > Meski > > > > "Going to Starbucks for coffee is like going to prison for sex. Sure, > > you'll get it, but it's going to be rough" - Adam Hills > > -- > silky > > http://www.programmingbranch.com/ > -- regards, Preet, Overlooking the Ocean, Auckland
