Hi Greg, I've worked on a project which has done the scripts in source control approach. I think the thing which made it work was that part of the CI build was to actually spin up a new db and run all the scripts. Failure of the scripts to run triggered a build failure and appropriate blame placed on whoever was responsible (i.e. ridicule and requests for free drinks).
ciao, Richard On Mon, May 31, 2010 at 11:14 AM, Greg Keogh <[email protected]> wrote: > Folks, I’m sure we’ve all had problems where multiple developers change > SQL Server scripts and they get out of whack and waste time with stupid > errors. > > > > I’m starting a fresh app and I thought I’d experiment with keeping scripts > in SVN. It just means that we have to remember to always save a script to > the source controlled file whenever it’s changed. > > > > Because scripts aren’t compiled source code, there is still the risk of > human error in not pushing any updated script files into the DB. I was > thinking of concocting a utility which automatically pushed changed scripts > into the DB, but before I start fiddling I thought I’d ask about this > subject in general first. Are there others out there who source control > their DB scripts and have techniques for reducing human error? Or perhaps > there are better techniques that I’ve completely overlooked. > > > > Greg >
