Re: Why an organization would need an enterprise DB team

Estifan,

I think what they are trying to accomplish is to get DBA work closer to the application people. Usually your opportunity to influence design is near the beginning. If you only review their design before it goes into production, usually they are close to a deadline and no time to modify anything.

    One suggestion would be to have the application DBAs sit with the application developers but still report to the central team. Also you could suggest that DBAs be rotated so everyone isn't stuck on 24/7 support all the time, and get a chance to broaden their skills.

    Some organizations have the position of architect.

Dennis Williams

On 3/17/07, EPA <epanosian_at_gmail.com> wrote:
>
> Hi guys,
>
> I guess I was not enough clear. The coming re-org wants to separate the
> DBAs between 1) operational (backup, recovery, upgrade...) and 2)
> application (logical design, physical design,...) and move the 2nd group to
> application services team. This means they will report and follow AS
> managers/directors. And I would like to proof and keep them in one group.
>
> I don't have any doubt about having DBA competency in development team,
> what I am looking is the cons if we separate the team and pros if we keep
> them together.
>
>
>
> Thanks again,
>
> Estifan Panosian
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/723 - Release Date: 3/15/2007
> 11:27 AM
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.12/724 - Release Date: 3/16/2007
> 12:12 PM
>

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