It wouldn't seam to me that one cannot substitute a particular join type for
another. An inner and outer join return two different recordsets.
You might take a look at the underlying table indices to ensure best
performance. My experience showed that certain composite indices produced the
best results ... all based on what the original query is. If your using
MS-SQL check the generated execution plan to see which if any indices are
being applied ... and watch out for table scans.
Another option, at least in 6.5, if you have ample server memory is to pin
the index in memory.
Try different index combinations and try a benchmark perform as best as you
can.
Bill Reichard
Willow Gold
[EMAIL PROTECTED]
http://www.willowgold.com
In a message dated 1/9/01 2:07:25 PM Eastern Standard Time,
[EMAIL PROTECTED] writes:
> What would be faster an inner join, an outer join, or a where
> something = something join. I am working with huge queries and a little bit
> of time on a small query could translate to a huge gain on my joins.
>
> Robert Everland III
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
