Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Developer responsibilities

Re: Developer responsibilities

From: Vladimir M. Zakharychev <>
Date: Mon, 29 Jul 2002 14:18:03 +0400
Message-ID: <ai34oq$5e9$>

As with any other tool, developers should learn it first, understand how it works and what this means to them. There are good books on Oracle besides the documentation, with Tom Kyte's "expert one on one: Oracle" being among the best and highly recommended, as it is targeted specifically at developers rather than DBAs. For example, the fact that your team is proficient with SQL Server means that they indeed should learn how Oracle works - these two are so different that some key practices considered good for SQL Server only do harm in Oracle. If they don't - you'll see performance problems, scalability problems and odd errors like ORA-01555 in applications they will develop using their SS skills...

As of developers being requesting access to production server - not really a good idea unless they are absolutely certain what they do and will claim all responsibility if anything goes wrong (well, someone has to roll out all those changes and patches anyway, but it better be done in controlled manner, with backup in place, and these changes should be tested and verified elsewhere before being applied to production system...)

My $0.02

Vladimir Zakharychev (      
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.

"sued" <> wrote in message news:AZB09.83$

> We are a shop that is new to developing on Oracle. Does anyone have
> suggestions / documentation that details what kind of responsibilities a
> developer has to create objects / forms / reports / etc on an Oracle
> platform? Performance tuning queries and utilizing explain plan have been
> brought up. As a newbie Oracle DBA I'm not sure how to guide the developers
> and we want everyone to do their job well.
> We currently use MS SQL and the code is being phased out. We have many new
> developers, at different skill levels, and requests to access the production
> server. We have a development server to test on as well.
> Any help would be greatly appreciated!
> TIA--
Received on Mon Jul 29 2002 - 05:18:03 CDT

Original text of this message