Posted by Greg D. Moore \(Strider\) on 07/24/05 17:38

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns969D7068E9C05Yazorman@127.0.0.1...
> Greg D. Moore (Strider) (mooregr_deleteth1s@greenms.com) writes:
> > Remind me of the syntax on this?
> >
> > In any way, the temporary fix was fairly simple.
> >
> > In the query itself or the join (which actually is better in our case)
> > giving a JOIN hint (doesn't really matter which one I use) immediately
> > improves the performance of the query.
> >
> > So for now we've added the hint to the VIEW.
>
> Glad to hear that you got it working.
>
> If the solution was to change:
>
> a INNER JOIN b
>
> to
>
> a INNER LOOP JOIN b
>
> there is a side effect: the tables will now be accessed in the order
> they appear in the query. This may be good for now, but further along
> the road, this may not be the best query plan.

Actually it's an outer join and using HASH or MERGE seems to work fine.


>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]