Jonathan.Trumbull_at_abbott.com (Jonathan D. Trumbull) wrote in
news:266c2da3.0210300447.3973909d_at_posting.google.com:
> Pablo Sanchez <pablo_at_dev.null> wrote in message
>
>> That's a bit ... absurd! <g> What seems to be happening is that you
>> have a full in-memory tablescan.
>>
>> Have you considered bulk loading the data into a 'scratch' table, then
>> doing a join back to SomeTable? I suspect it'll be tons faster!
>>
>> Thx!
>
> Unfortunately, it is not me who is generating the SQL. We are using
> a third party tool that sits on top of the DB. It generates this
> monster....
Ack, isn't tht always the case ... when you run a full table scan on
the table, does it take the same amount of time? If not, sounds like
a bug and since you don't have the source code, you're only bet is
going to be to log a call with Tech Support.
--
Pablo Sanchez, High-Performance Database Engineering
http://www.hpdbe.com
Received on Wed Oct 30 2002 - 07:50:39 CST
