Re: Too many foreign keys...!

IMO you definitely shouldn't drop the foreign keys. They allow Oracle to use row-level locking in constraint checks instead of table level locking.
I'm currently working with an application ALL constraints in the form of triggers. Performance is bad, parsing overhead is high. select count(*) from detail table everywhere, where the count can result in thousands of rows.
IMO, you don't want this.

Hth,

--
Sybrand Bakker, Oracle DBA
Sanaa BELBAGRI <belbagri_at_ispalliance.net> wrote in message news:37FA4893.37E8F0CA_at_ispalliance.net...
> Hi all,
>
> I am implementing a database using ORACLE and I have a problem.
> One of my tables contain 5 foreign keys moreover it's supposed to be one
> of the biggest and most accesible table in the application.
> So I wonder what can I do to avoid the problem of a very bad performance
> in term of access to the table (for example withdraw the foreign keys
> and treat the problem on the programming side by testing everytime the
> data entred,....etc).
> Can you help?
>
> Many Thanks
>
>
>
>
>
Received on Tue Oct 05 1999 - 14:27:02 CDT