Re: Deadly sins againts database performance/scalability

Dusan Bolek wrote:

> Hello,
>
> I'm just creating some document how developers should/must not behave
> when dealing with Oracle database. I written down some basic rules and
> came with idea what's the most stupid thing that you can do to your
> database.
> I have two on mind, first one is not using BIND variables and the
> second one is using COMMIT in a loop statement. However, there will be
> more of these.
> So I have question to you here. What's the most stupid, but in real
> world foundable, mistakes in development applications using Oracle
> datatabase?
>
> --
> with regards
>
> Dusan Bolek

Having read everyone else's list.

1. Developers that don't understand the implications of the multiversion concurrency model.
2. Developers that don't understand the implications of reads not blocking writes and writes not blocking reads.
3. DBAs that don't understand the implications of ORA-01555.
4. Those schooled in other RDBMS products that insist on treating Oracle as if were the other product.
5. Organizations that don't conduct code reviews.
6. Developers of testing prorams that can't read code and don't know how to identify potential weaknesses and test for them.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)