Hi, The built in archiving has its pros and cons. The main advantage is that the archive form will automatically be updated when you add/change fields to the source form. Or at least this is how it is supposed to work. The cons are: - that you do not retain the Request ID (field id 1) in the same field as the original - you can not merge/modify records in the archive form - you are a little limited on how you do your archivning
Except that the archive form is updated when you change your source-form, you can make a more flexible solution with escalations and push-fields. If you want to retain the Request ID as field id 1, you can use DSO or some other tool, such as our free rrrChive-utility downloadable at from our website at https://www.rrr.se/cgi/rrrchive/main. For systems with a lot of records, I have often used a 3-tier-archiving strategy that looks something like this: 1. ActiveTicketsForm (all open tickets plus 1 month worth of closed tickets) 2. ClosedTicketsForm (all closed tickets for 13 months) 3. ArchivedTicketsForm (13 months and older tickets) The ClosedTicketsForm is used for most reporting and to get statistical data. The referencial integrity is kind of tricky, as the referencese are built by workflow objects. This may make it simpler, as the order in which you move children is not important. On the other hand, there may be a filter that i.e. deletes child records when the parent is deleted. You have to analyze the workflow objects such as push-fields from the parent-form, tables and join-forms in order to determine what child records are releated to the specific parent-form. Also check to see if you have any filters triggering on delete on the parent-form. These filter may be in place to delete the some or all of the child-records. Best Regards - Misi, RRR AB, http://www.rrr.se > Hello everyone: > > What are the advantages and disadvantages of archiving Helpdesk 5.6 > application data using the different possible options? > > If I use DSO (Distributed Server Option) to push tickets to another form > on a different server or the same server. > > If I export the data to external files (.arx and .def files) and store > these in a folder on the server. > > If I make a copy of the form (using File - Save Form As). Create an > escalation that checks for records meeting a specific criteria . The > escalation would push the data from the original form to the copy form. > and delete the original entry using Application-Delete-Entry once the > record has been archived to the copy form. > > If I use the AR Server version 6.3, new Archive feature to automate the > process of archiving records. I can create an archive form that mirrors > the original table.I can assign a Run If statement and specify the > conditions and specific data to be archived as well as automate the > deletion of the original record. > > or If I run an archiving escalation with a qualification such as ($ > TIMESTAMP $ - 'Date/Time Closed')> ((30*24)*3600) ( select all tickets > which have been closed for at least one month). > > My other question is about referential integrity (Please excuse my lack > of experience working with Remedy products if the following questions > are not making any sense). > > Do I create escalations to archive the children records first then > delete these children records and then archive and delete the parent > schema records?. How do I know what are the tables (schemas) that > contain the children records for the parent. Is HPD:Helpdesk schema the > parent?. From my previous experience about deleting records from a > database (other databases besides Remedy) I always had to delete the > children records before I could delete from the parent table so that > "orphans" records not violate the referential integrity rules. How do I > find information about these relationships?. In other words what tables > (schemas) in the Helpdesk application need to be archived and if there > are several schemas what is the order of archiving. > > Environment: --- AR system 6.3 --- Microsoft Windows server 2003 --- > SQL server Database --- Helpdesk version 5.6 > > > > Thank you. > > > > > > > > Portions of this message may be confidential under an exemption to Ohio's > public records law or under a legal privilege. If you have received this > message in error or due to an unauthorized transmission or interception, > please delete all copies from your system without disclosing, copying, or > transmitting this message. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
