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
...@ozdotnet.com] *On Behalf Of *Jano Petras
*Sent:* Tuesday, 1 June 2010 8:15 AM
*To:* ozDotNet
*Subject:* Re: Source control of DB scripts
Greg,
An approach that worked well in the past for me was:
* No permission to execute DDL statements on staging / dev databases given
to the developers
, 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
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
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
. 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
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
--
Michael M. Minutillo
Indiscriminate Information
