Following solution works fine except db2 database, for db2 customer has to run runstat on db for T table in question and understand where exactly the time is taken, based on the output of runstat customer can implement indexes.
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Ashtaputre, Anay Sent: Wednesday, January 09, 2013 1:54 PM To: arslist@ARSLIST.ORG Subject: Re: Long Running Query ** Following Defect & Knowledge article can be referred - SW00443560 KA380785 Following fields will need to be indexed - 'C230000009', 'C1000000079' & 'C7' Indexing to be done at the db level for better performance and after indexing customer should get 'execution plan' aka 'explain plan' of the query by running it on db directly and see the time difference between pre-indexing and post-indexing. That will tell you whether or not solution implemented is helping. Thanks Anay.. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Vishal Navale Sent: Wednesday, January 09, 2013 1:13 AM To: arslist@ARSLIST.ORG Subject: Re: Long Running Query ** Thanks Rick for the answer. Modify the query and indexing - do you have some suggestions for how to do this. Thanks Vishal On Tue, Jan 8, 2013 at 2:00 PM, Rick Cook <remedyr...@gmail.com<mailto:remedyr...@gmail.com>> wrote: modifying the query, _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
