On Tue, 25 Nov 2003 08:03:58 -0800, Dusan Bolek wrote:
> Hello,
>
<SNIP>
> So I have question to you here. What's the most stupid, but in real world
> foundable, mistakes in development applications using Oracle datatabase?
- Not taking backups :o)
- Adding indexes all over the place for performance reasons.
- No (proper) change control procedures.
- Exporting from the database and defaulting COMPRESS to Y, even worse,
exporting with COMPRESS=Y explicitly.
- Allowing developers to create obbjects in a tablespace with a
different extent size to the tablespace defaults.
- Having numerous indexes (on the same table) which could be replaced by
one or two carefully thought out indexes. (you know, indexes on A and B
and A,B and C and A,B,C and B,C ....)
- Putting the ref int checks in the application instead of the database.
- Ditto, but keeping business rules in the app instead of the db.
- Using standalone procs and functions instead of packages.
- When actually writing packages, not separating the PACKAGE specs from
the PACKAGE BODY so every time you change the code in a body, you
re-create the spec as well and invalidate everything that depends upon it.
- Using a table to hold a sequence number is a bad one. You know, read
the number and lock it, increment it and write it back - then commit at
some point in the far future. Even committing ASAP is a major problem as
soon as you get more than 5 or so users all doing the same thing.
- Even worse, having a single table for all the sequence numbers in the
system.
- Creating 'temporary' tables to hold intermediate results MS SQL Server
style.
- Converting triggers from another db system into Oracle and discovering
that the other system allows you to update rows in the table that has
triggered the trigger leading to mutating table errors on Oracle (which
IMHO does it correctly !)
- Not enough SQL reuse.
I'm sure that there are more :o)
Cheers,
Norm.
--
Delete the obvious bit from my email address to reply by email.
Received on Tue Nov 25 2003 - 10:35:59 CST
