Hello Jorge,

 

I am currently working on an application that will allow Parent-Child
archiving with synchronization of fields and views. 

(on top of other options like: creation of destination table with ALL or
DATA ONLY fields, enable/disable index and filters, scheduling, specific
restore, .)

It will support ARS version 5.1.2 and later.

I could send you a demo when it is completed.

Target completion date is May 31st.

 

Please let me know if you are interested.

 

Best regards,

 

Pierre Lafortune

Urantia BTT Inc.

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Jorge Polo
Sent: Tuesday, April 24, 2007 2:48 PM
To: arslist@ARSLIST.ORG
Subject: archiving data

 

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.

__20060125_______________________This posting was submitted with HTML in
it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to