Change the second query from
('A' = $A$) AND (NOT (('Status' = "Resolved") OR ('Status' = "Closed")))
to
('A' = $A$) AND ('Status' < "Resolved")This may be slightly more efficient than the other. Give it a shot.. Joe ----- Original Message ---- From: Chintan Shah <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Monday, September 8, 2008 4:52:15 PM Subject: Re: Latency on Search ** DBA ran the queries against the DB on reporting server and it took 25 seconds! No wonders, I turned on DB logs and found the same execution period. Cant access DB from sqlplus as we are not granted permissions to touch Oracle outside of Remedy. Again ran the same queries on production server DB, it was <1 second. 'Status' field has following options 1.Assigned 2. Work In Progress 3. Resolved 4. Closed 5. (clear). Thanks Chintan --- On Mon, 9/8/08, Axton <[EMAIL PROTECTED]> wrote: From: Axton <[EMAIL PROTECTED]> Subject: Re: Latency on Search To: arslist@ARSLIST.ORG Date: Monday, September 8, 2008, 1:27 PM ** Run the query against the db and get the db statistics from the two servers. Use sqlplus and type 'set autotrace on', then run the query, this will give the execution plan and statistics. Post the plan and stats from each server. Axton Grams On Mon, Sep 8, 2008 at 4:14 PM, Joe DeSouza <[EMAIL PROTECTED]> wrote: ** What are the different statuses you have on that form? Can you please enlist them in the order they appear? Joe ----- Original Message ---- From: Chintan Shah <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Monday, September 8, 2008 3:49:42 PM Subject: Re: Latency on Search ** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
