If you have some typical queries, you can use OEM to create a virtual index
with the extra column. Then for each query you can get a side-by-side
comparison of the explain plans with the existing index and with the virtual
index.
"Ted Chyn" <tedchyn_at_yahoo.com> wrote in message
news:44a19320.0308071151.155f6b02_at_posting.google.com...
> Sir,
>
> Can any one shed the light on following FK question.
>
> Table1 primary key c1
> Table2 contain foreign key constraint for c1 from table1
>
> Generally a index need to be created on c1(table2) for many reasons.
> My question is what kind shortcoming and potential problem I may
> encounter, if I create an index on c1 + another column on table2 -
> sort of like partial foreign key index ?
>
>
> thanks a lot
> ted
Received on Thu Aug 07 2003 - 15:37:59 CDT
