Re: What to tell the new programmers?

Sybrand Bakker wrote:

> On 19 Jul 2002 10:10:43 -0700, pmc_at_finger-rock.com (Patrick Connors)
> wrote:
>
> >I've been detailed to give a talk and question/answer session to the
> >rest of the programming team on Oracle Best Practices/Tuning. I'm
> >accumulating a mountain of material and am not sure where to start.
> >The audience is people who can write fairly complex queries, but don't
> >consider themselves Oracle specialists.
> >
> >I've got topics like:
> >"How to develop sql to use the optimizer well",
> >"How to do and read an Explain Plan"
> >
> >New user stuff.
> >
> >So: If -you- had an hour to fill with this audience, where would you
> >start?
> >
> >Thsnks.
>
> I would start to explain to use bind variables and dwell on that for
> the rest of the hour.
>
> Regards
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address

I agree. And make sure they have SQL statements handed to them so that they know how to look at what they have done and see if Oracle is treating it as they expect.

Then in the few remaining minutes don't just tell them about explain plan make it mandatory and make them send the explain plan for every SQL statement to the DBA as part of the approval process.

Then demonstrate the use of DBMS_Profiler and make that mandatory too.

Finally ... institute code reviews before any code is written and before any code goes to QA.

Daniel Morgan Received on Mon Jul 22 2002 - 10:20:11 CDT