On Tue, Mar 10, 2009 at 9:15 PM, Steve McLellan <smclellan(at)mintel(dot)com> wrote:
> Thanks - the nested loop is indeed causing problems - reducing
> seq_page_cost had the same effect of removing the nested loop for this
> query. We'd noticed the poor row count estimation. Increasing the statistics
> doesn't seem to have much effect, but we'll have more of a go with it.
More than likely it's the sequential page cost versus the cpu_xxx cost
setttings that's really making the difference. I.e. if you raised the
cpu_xxx settings you'd get the same result. But I'm not sure, just a
guess.