Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Outer joins, performance penalty?
USUALLY your outer join operations are going to be more expensive than the
inner joins. Since you are going to be retrieving more data. But assuming
that the columns are indexed and not null then it shouldn't be a problem.
If you need to outer join then I would outer join, but if you don't I
wouldn't.
Jim
"Preston Crawford" <prestonc_at_REMOVESPAMBLOCKcrawfordsolutions.com> wrote in
message news:slrnaebb1s.5hr.prestonc_at_serpentor.local...
> MS SQL Refugee here, so bear with me. I'm new to Oracle and writing a
> function to return a cursor with the result set of a join of multiple
> tables. In MS SQL I'd just use the outer join syntax and I guess I'd never
> thought of the possible penalty of this. In the course of searching online
> for the Oracle syntax, a few people made a reference to the idea that for
> every outer join a table scan is performed on the table being joined in
> optionally. So I'm wondering, is this true? And if it is true, what is the
> solution?
>
> Preston
Received on Fri May 17 2002 - 22:25:02 CDT
![]() |
![]() |