Re: Index Across Tables

"Mark Townsend" <markbtownsend_at_attbi.com> wrote in message news:B94BA0FD.38A91%markbtownsend_at_attbi.com...
> in article 3d2603e8$0$8510$cc9e4d1f_at_news.dial.pipex.com, Niall Litchfield
at
> niall.litchfield_at_dial.pipex.com wrote on 7/5/02 1:39 PM:
>
> > "Donna Yorukoglu" <dym7_at_outreach.psu.edu> wrote in message
> > news:8ede3df2.0207051122.7529f90d_at_posting.google.com...
> >> I have one multi-column index (using a concatenated datastore). Works
> >> great. However, I would like to either create a new index on another
> >> table and then join the indices or create one index across both
> >> tables. Are either of these options possible with Oracle 8.1.7? Any
> >> advice would be greatly appreciated.
> >
> > Joining indexes makes no sense. if you index the relevant columns then
(if
> > appropriate) oracle will use both indexes to get to the data.
> >
>
> Hmm - not necessarily. A join index (aka a materialized view across two or
> more tables) can be useful in some circumstances.

Materialized views are great. I don't think of them as indexes though?

> And the new bit mapped
> join indexes in Oracle9i rock.

care to expand. I haven't looked so this is a purely lazy question.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************