RE: Development guidelines between DBA & developer

In my current assignment, I was hired to do just this. That database is now in production and I am doing other things. But I agree that this does not happen any more - we end up getting database table requests one at a time. And by the time we are done, the database structure looks like crap.

-----Original Message-----
From: rjamya [mailto:rjamya_at_gmail.com]
Sent: Tuesday, April 12, 2005 10:45 AM
To: thomas.mercadante_at_labor.state.ny.us
Cc: AmihayG_at_ectel.com; Oracle-L (oracle-l_at_freelists.org) Subject: Re: Development guidelines between DBA & developer

On Apr 12, 2005 10:30 AM, Mercadante, Thomas F <thomas.mercadante_at_labor.state.ny.us> wrote:
> Amihay,
>
> Ideally, the Development DBA should be a member of the design team and
> should review all design specs. The DBA should be the person to design
the
> database tables and deliver them to the developers. The DBA should be
> available to the developers as a resource for writing PL/SQL objects and
> tuning sql.

In real life, the above is almost always a hypothetical case, barring few exceptions. Anyone has experience otherwise? This is almost like to economists _agreeing_ on something.

Raj

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