Re: Development guidelines between DBA & developer

Hi,

in-line

On 4/12/05, Amihay Gonen <AmihayG_at_ectel.com> wrote:
> Hi all,

>=20
...
> I'm looking for an optimal way for defining the work between the developm=
ent
> team and the DBA teams.

...
I don't know about writing documents about these topics. How about some practical tips?

I like to create metalink (dev) accounts for developers, but not give tars. Also, I try to point out good books to developers regarding Oracle. If successful, I don't have to answer many questions about re-inventing referential integrity and sequences. ;-)

Also, I download all the Oracle docs we might be using in a couple directory paths. Then I use acrobat to create indexes and teach the developers how to use reader version 7 and acrobat indexes to search the docs. I add the installation docs to the fat pdf libraries, and include multiple platforms. My indexes include more stuff than Oracle's acrobat indexes. Then I put the files on a windows server share, and shortcuts with //server/file paths as icons in another directory. The developer's can map the drive once, copy the shortcuts to their desktop, and drop the mapped drive.

It paid off this week when they found out how to check open cursors, and it wasn't their application (like I thought, oops) but rather EM sessions opening hundreds (thousand+) of cursors. We have our warning level set low on 10g alerts, and I didn't check because I was lazy and they caught me. It feels good to get good questions, and especially good to be caught in a mistake.

If the development database is safely isolated then more freedom can be given developers. If servers are shared, I'd lock the servers down harder. Have a backup and recovery plan for development, different than production.

HTH Regards,

Mike Thomas

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