Oh, forgot to mention: set up an escalation to initially fill the values -- then use the workflow afterward. a one time run.
On Thu, May 22, 2008 at 7:42 PM, patrick zandi <[EMAIL PROTECTED]> wrote: > How about an extra field instead. > Why not just add a Search "value". When the form is saved, (filter) and it > meets the below Qual, Unset the field or set field to the value S1 or even > use Selection Field Like I have. > > What I did was put in a Selection field > Search O Type 1 O Type 2 O Type 3 O Type 4 > Each selection field is on when it meets the qual for the query. > (in this case they need to different) > The when you do a query it is based on the = and not the != > > -- Hope I am making sense.. It just depends on how many you need.. > Maybe a Character field with 2 values - Your own Index so to speak. > Then you have 99 choices - which means no need for an index. > > Just a thought. > It is just Workflow Dependent. I have used this before and it was amazingly > fast. > > On Thu, May 22, 2008 at 12:38 PM, Robert Halstead <[EMAIL PROTECTED]> > wrote: > >> ** Ladies and Gents, >> >> We have been constantly trying to improve performance on a form with over >> 1 million records in it by analyzing indexes, or clearing the statistics for >> the table in oracle. The last thing we did was clear the statistics for our >> form BZ:Incident because for some reason searches in Remedy, even though we >> were searching on index fields, were not using the indexes in Oracle. By >> clearing the statistics, I believe we're forcing oracle the use the indexes >> resulting in the searches . However, searching on a field that is not >> indexed now performs a database time out error in Remedy. >> >> My question: Where is the happy place? When you guys analyze statistics, >> to what percent? Also, how often do you find yourself analyzing indexes? >> >> On a related question, performing searches in Remedy using the != operator >> does not utilize the index for that specific field. I'm performing a search >> on a form where 'Parent' = $NULL$ and 'Link Type' = $NULL$ and 'Incident ID' >> != $tmp_IncidentID$. Essentially I'm wanting to return all tickets that are >> not associated with a parent and not return the incident I'm trying to >> link. >> >> How would I change this query so that I utilize the indexes? The search >> seems to perform a full table scan against the table in oracle. All three >> fields are indexed on the form. >> >> I sure that this is covered in the Performance and Tuning class, I just >> have yet to take it. >> >> Environment: >> AR System 6.3 Patch 20 >> Oracle 9i >> >> -- >> "A fool acts, regardless; knowing well that he is wrong. The ignoramus >> acts on only what he knows, but all that he knows. >> The ignoramus may be saved, but the fool knows that he is doomed." >> >> Robert Halstead __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the >> Answers Are" html___ > > > > > -- > Patrick Zandi > > Dev Technology Group --> www.devtechnology.com > Exceeding your Expectations ! By Design... -- Patrick Zandi Dev Technology Group --> www.devtechnology.com Exceeding your Expectations ! By Design... _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
