DBAsupport.com Forums - Powered by vBulletin
Page 3 of 3 FirstFirst 123
Results 21 to 23 of 23

Thread: Insert taking too much of time.

  1. #21
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Jurij,

    Could you workout anything based on query and Explain plan?

    Thanks,

    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

  2. #22
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Hi Sam,

    I just tried to indent your explain plan into some meaningfull form, but have given up. 9-table join to tune - no offence, but no, thanks. I'm not in the mood to dig into this., Without having a slightest idea of how many rows each of this table hav, which indexes are available, etc..., I'm realy not in the mood to dig into this. Sorry.

    The best advice I can give you is to have all those tables fully analyzed (compute) and then let the optimizer decide the best execution plan.....
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  3. #23
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938

    The best advice I can give you is to have all those tables fully analyzed (compute) and then let the optimizer decide the best execution plan.....
    Strangely enough, I, and some other people have noticed that probably ESTIMATE might be better than COMPUTE at least on 8i. I have followed long running queries on the same DB analyzed with ESTIMATE and with COMPUTE. The better results were achived with ESTIMATE. Anyone else noticed something similar?


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width