Re: Development guidelines between DBA & developer

this varies from shop to shop and depends whether its an oracle developer or a software engineer(java, .net, etc...) i am typically on the development time. I have been on projects where I have had OSDBA access in production where I did all the DBA work accept installs, DB copies, and backups. I could handle recoveries if there was an emergency.

been on other shops where i was the production DBA and the development team didn't have any access to production.

on my current one I am a development DBA, I have limited production access. Varies from shop to shop. Depends on the people on your team and what they know. Depends on security rules if you are doing say financial data or government stuff.

i dont think you should have an across the board rule. Depends on the shop and the people on it.

• Original message --------------

> Hi all,
>
> I'm looking for guidelines , how should be the interactions between DBA
> team and other development teams.
>
> For example -
> Each new table has to have description ...
> Define table main queries ..
>
>
> I'm looking for an optimal way for defining the work between the development
> team and the DBA teams.
> I'm aware of , that for every company , there are some differences , but I
> think that there are some big common between the guidelines.
>
>
> I define a developer , as person with a medium knowledge in oracle , and
> expert in software engineer.
>
> DBA - as the opposite.
> Amihay Gonen
>
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l

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