Database Change Control Process
- From: Jeff C <backseatdba@xxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 25 Feb 2014 08:25:43 -0800
I am curious how everybody handle database change control. I am not
talking about just source control for your code but the process of moving
changes into the database, like procedure changes, alter tables, indexes,
manually update of data, etc. Do you have a formal process to go through
and what is that like if you are willing to share.
We are a private company so things have been kind of light here and we
don't have any credit card data. We source control, plus we have a
project/bug tracking program that most but not all code changes are related
to, and then all code is reviewed before moving to production. Oh and I
have a ddl trigger enable to save all updates. But I don't feel like all
of this tells a true story. I think we need something more formal and I am
trying to gather ideas and opinions before I move forward with the idea.
Thanks for any input.
Jeff
Other related posts:
