I am not sure you may find Best Practices out there for such a thing. Its more a matter of business requirement than a best practice.. Consider the following questions that come to my mind:
What does your business need? When would a ticket be deemed to fit as an archive? What are the conditions for archiving a ticket? Age of the ticket? The time since the ticket was last retrieved (I wish ARS had a way to mark this without actually modifying a tickets Last Modified Date without running a Direct SQL)? The time since the ticket was actually modified? The time since the ticket has been in a particular status - say Closed? Maybe skip archiving tickets that had been marked as Closed by the AR_ESCALATOR user as there may be a possible need for reopening them?? These are just examples.. To support these needs you may need to build hidden data fields to contain information that could drive your qualifications to archive a ticket. For eg your qualification could be archive any ticket that hasn't been modified for the past 4 months AND have a Closed Status.. It really boils down to what you need so I would start looking there rather than looking for some industry standard Best Practice for archiving business information.. Cheers Joe ----- Original Message ---- From: Timothy Rondeau <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, October 15, 2008 2:53:18 PM Subject: Best Practice for Archiving ** Hi, We want to start looking into the best practice of Archiving. We are on 7.0.1 patch 2 SQL 2000, ITSM suite. Mainly I can see the Worklog and the Notification Log are huge, need to get this data archived. Looking to see what others have done to handle this and how well that has worked. Thanks Tim _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
