🚀 go-pugleaf

Thank you all

I solve it by using EXISTS instead of IN, that makes the speed acceptable.
I use the Interbase PLANalyzer for testing the store procedure plans and it 
give me a good result. but when using that procedure with IN, like my 
example, the IN statement doesn't use the any index and it make a full scan 
many times, but when using the -exists - it make only one full scan.

Select *
From MyStoreProcedure
Where foo1 = foo2
and foo3 = foo4
and foo5 = foo6
or EXISTS (Select ID From MyTable Where f1 = f2);

Bye.


"Safwan" <safwan_maswadeh@yahoo.com> wrote in message 
news:47bcbe87@newsgroups.borland.com...
> Hi
>
> Select *
> From MyView
> Where foo1 = foo2
> and foo3 = foo4
> and foo5 = foo6
> or ID in (Select ID From MyTable Where f1 = f2);
>
> With the above statement the speed is acceptable. But when changeing the 
> same view (MyView) into a store procedure with  - for select .... from ... 
> do suspend. - like this :
>
> Select *
> From MyStoreProcedure
> Where foo1 = foo2
> and foo3 = foo4
> and foo5 = foo6
> or ID in (Select ID From MyTable Where f1 = f2);
>
> The statement take a looooong time to fetch the records.
> I use the PLANalyzer to check the statement, I notice that the in clause 
> cause slow.
>
> What should I do to speed up my query ??
>
> Your's
> Safwan.
>
>