Re: Episode 2: the EntMgr Green Light!!

If you delete from the parent table and there is no index on the fk in the child, the child table will get a share lock, preventing other exclusive locks -- this can lead to chaos. Also the share lock won't kick in until there are no other locks on that table.

The index should be there unless the parent table is read only. As for the index rebuilding stuff, like I said, the main argument comes from a pctfree setting that is too low -- don't blame the rebuild itself.

Dom.

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<bol9d6$gq3$1$8300dec7_at_news.demon.co.uk>...
> Your comment needs a little clarification.
>
> It is a bad idea to create an index on a
> set of columns simply because that set
> of columns represents a foreign key constraint.
>
> Indexes should be created if, and only if,
> they add value. Indexes "on foreign keys"
> do not necessarily add value.
>
> --
> Regards
>
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> The educated person is not the person
> who can answer the questions, but the
> person who can question the answers -- T. Schick Jr
>
>
> One-day tutorials:
> http://www.jlcomp.demon.co.uk/tutorial.html
> ____Belgium__November (EOUG event - "Troubleshooting")
> ____UK_______December (UKOUG conference - "CBO")
>
>
> Three-day seminar:
> see http://www.jlcomp.demon.co.uk/seminar.html
> ____UK___November
>
>
> The Co-operative Oracle Users' FAQ
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
>
> "Domenic G." <domenicg_at_hotmail.com> wrote in message
> news:c7e08a19.0311081901.60899479_at_posting.google.com...
> >
> > Next thing you'll say it's not a good idea to index FKs.
> >
Received on Sun Nov 09 2003 - 09:51:41 CST