There are some pretty severe Oracle performance problems we had to address - the "Push fields if" filters that fire to populate the form end up causing many, many table scans.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Phil Murnane Sent: Friday, December 19, 2008 12:44 PM To: [email protected] Subject: Re: Archiving SLM:Measurement ** William: Sounds like a pretty good solution to me. Just out of curiosity, are you seeing performance problems due to the 4.5M records in SLM:Measurement? --Phil ________________________________ From: William Rentfrow <[email protected]> To: [email protected] Sent: Friday, December 19, 2008 10:35:06 AM Subject: Archiving SLM:Measurement ** It's Friday and I have some other stuff to finish today so I haven't gotten too far into researching this yet - so I thought I'd ask if anyone else has a solution for this already. Problem: SLM:Measurement is gigantic. We have 240,000 requests in HPD:Help Desk (IM 7.x) and 4,400,000+ SLM:Measurement records. My gut feeling is to just archive off all of the records that are closed and refer the reporting people to that table when they want to run reports; however, I have not yet investigated the ramifications of doing this. Has anyone else? William Rentfrow Principal Consultant, StrataCom Inc. [email protected] 701-306-6157 C 952-432-0227 O __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
