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@xxxxxxxxx] Sent: Tuesday, April 12, 2005 10:45 AM To: thomas.mercadante@xxxxxxxxxxxxxxxxx Cc: AmihayG@xxxxxxxxx; Oracle-L (oracle-l@xxxxxxxxxxxxx) Subject: Re: Development guidelines between DBA & developer On Apr 12, 2005 10:30 AM, Mercadante, Thomas F <thomas.mercadante@xxxxxxxxxxxxxxxxx> 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 -- //www.freelists.org/webpage/oracle-l