Re: Schema updates - roles

David,

I have indeed worked with some developers with skills I greatly respected. However, I think that operations need to be separation from development. Many organizations are moving to incororate the ITIL model. Basically for DBAs this often means three databases:

1. Production database
2. Test database. A recent clone of production.
3. Development database. The developers can do what they want in the development database. The results of their development is a set of scripts to be applied to production. The person responsible for updating production will take those scripts and instructions and apply them to the test database. Then users test against the test database. Once everyone is satisfied, a production upgrade is scheduled and carried out by the same person who applied the scripts to test. One final argument for separating duties. Today your developers may indeed be top-notch. However, tomorrow a big project may be started and many contractors hired to develop on the new project. If you have a history of developers updating production, it may be difficult to clamp down on some cowboy developer before they trash your production.

Dennis Williams

On 3/27/07, David Green <thump_at_cosmiccooler.org> wrote:
>
> I would like to hear you arguments for DBA Ops performing Application
> schema
> updates versus Developers.
> Keep in mind the skillset across both teams is top notch and updates go to
> non prods first.
> How do you define the roles and responsibilities in your org specific to
> this subject?
> What pros and cons do you embrace in such a discussion?
> Thanks for any feedback.
>
> David
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l