October 25, 2006 at 10:10 am
I would also like to see the query run with the following set and see what it says.
set statistics io on
set statistics time on
It will give you the io on the tables in the query. A little better judge at poor performance when used in conjunction with the execution plan.
Tom
October 25, 2006 at 12:49 pm
Aaron West, thank you for such a comprehensive list of things to try. My hours are limited for this test, and when I executed the actual query on production there were two things to notice... 1) the explain plan was TOTALLY different than on test... and 2) it took 1:03, not the "5 minutes" I had been told.
That said, I am not sure the hours (read that "charge number") are available for additional improvement.
Your tips have been passed on to two developers who will consider pieces of it in the big picture.
Thank you again, so much, for your response. You are greatly appreciated.
David
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
October 25, 2006 at 12:56 pm
Stephanie, Ed and Tom,
Thanks also for taking the time to respond to my post. I do apprediate you very much. The information on the inner join was particularly interesting. Hopefully we will get the chance to see some improvement with these changes. As with Aaron's post, your posts have also been forwarded to the developers and they will try to understand and implement them, as possible.
I won't be running the explain plan again unless I can do so on a copy of the DB. The backup file is 5.5 GB and the last time I tried to download one of them here it caused heartburn. They may have to FedEX a disk to me.
At any rate, my hours are up, for now, on this problem.
I do apprecaite your responses, and those of others who posted. Thank you all very much.
David
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply