Fortunately, you have a 'fix' for yours...just index the darn field...:) _____
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Meyer, Jennifer L Sent: Thursday, July 02, 2009 9:36 AM To: [email protected] Subject: Re: Rant: RE: SW00327272 ** As always, Jason, your insight into the depths of the corporate mind astounds and delights me. Jennifer Meyer _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Sent: Thursday, July 02, 2009 11:30 AM To: [email protected] Subject: Re: Rant: RE: SW00327272 You're missing the point. This is just 1 of the built-in job security features that BMC has so kindly built into ITSM for us high by consultants and developers. :-) Jason _____ From: "Meyer, Jennifer L" <[email protected]> To: [email protected] Sent: Thursday, July 2, 2009 6:20:34 PM Subject: Re: Rant: RE: SW00327272 ** BMC has created defect # SW00329945 for the issue you have reported. Yes, this past May. Actually, this one was rather straight-forward. The notification audit table timed out every time it was refreshed. When I checked the qualifications, the field it was searching on was non-indexed. Other forms' notification audit tables search on an indexed field, e.g. HPD:Help Desk Audit Log, CHG:Infrastructure Change Audit Log. Just TMS:Audit Log doesn't search on that field: it has its own special guid field. Come to think of it, I think one of the users told me a week or so ago that one of the Problem audit logs is timing out as well.. Jennifer Meyer _____ From: Action Request System discussion list(ARSList) [mailto: _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
