"Craig A. James" <[EMAIL PROTECTED]> writes:
> Is there some way to explain this cost to the optimizer in a permanent
> way,
Nope, sorry. One thing you could do in the particular case at hand is
to rejigger the WHERE clause involving the function so that it requires
values from both tables and th
I have a function, call it "myfunc()", that is REALLY expensive computationally. Think
of it like, "If you call this function, it's going to telephone the Microsoft Help line and
wait in their support queue to get the answer." Ok, it's not that bad, but it's so bad that
the optimizer should A
