Topic Options
Rate This Topic
#39614 - 12/29/00 10:58 AM Archiving Data
jsprenge Offline
enthusiast

Registered: 06/12/01
Posts: 243

Does anyone have detailed instructions on how to archive data from a form
and still keep it accessible? Opinions and suggestions needed. Thanks

Janie Sprenger
Remedy Administrator
Legacy Health System
Portland, OR
503-415-5826





Top
#39615 - 12/29/00 11:31 AM Re: Archiving Data [Re: skinsey]
Anonymous
Unregistered



Not detailed, but here is how we does it:

Created a 100% indetical form (no workflow at all), set all fields to read-only. When a ticket is set to Closed, this record is moved over to the archive form. In
the main form there is two field, listing the number of open and closed tickets. A button can be used to list all open or closed tickets.

In our control-panel the users can search for ie entry-id, the mcaro search first in the mainform, if no hit then it search in the archiveform.

--
Jarl Groneng
jgroneng@online.no


29.12.2000 08:58:58, "Sprenger, Janie : CO IR" wrote:

>**
>
>Does anyone have detailed instructions on how to archive data from a form
>and still keep it accessible? Opinions and suggestions needed. Thanks
>
>Janie Sprenger
>Remedy Administrator
>Legacy Health System
>Portland, OR
>503-415-5826
>
>
>
>
>
>





Top
#39616 - 12/29/00 01:40 PM Re: Archiving Data [Re: skinsey]
michael connelly Offline
Stealth Member

Registered: 06/12/01
Posts: 34

Something to be aware of with this archiving approach is that if you do FTS
then you are simply moving the data to another form causing is to be
re-indexed. Overall your server will always be working more on FTS
re-indexes because the amount of data never decreases. We have implemented
an archiving strategy where we export data yearly that is older than 3
years. In some of our other systems where the need to keep the data, but not
see it exists, we use a active link to set a flag no matter what the user
searches on. We have an escalation process that "ages" the records, and a
filter that sets the flag to true upon reaching a certain age.

M i c h a e l R. C o n n e l l y
The Johns Hopkins University Applied Physics Laboratory
11100 Johns Hopkins Road, Laurel, MD 20723
Phone: 443 778-7323, Fax: 443 778-1093
michael.connelly@jhuapl.edu


-----Original Message-----
From: Jarl Groneng [mailto:rapid@ONLINE.NO]
Sent: December 29, 2000 12:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Archiving Data


**

Not detailed, but here is how we does it:

Created a 100% indetical form (no workflow at all), set all fields to
read-only. When a ticket is set to Closed, this record is moved over to the
archive form. In
the main form there is two field, listing the number of open and closed
tickets. A button can be used to list all open or closed tickets.

In our control-panel the users can search for ie entry-id, the mcaro search
first in the mainform, if no hit then it search in the archiveform.

--
Jarl Groneng
jgroneng@online.no


29.12.2000 08:58:58, "Sprenger, Janie : CO IR" wrote:

>**
>
>Does anyone have detailed instructions on how to archive data from a form
>and still keep it accessible? Opinions and suggestions needed. Thanks
>
>Janie Sprenger
>Remedy Administrator
>Legacy Health System
>Portland, OR
>503-415-5826
>
>
>

>
>
>









Top
#39617 - 12/29/00 02:00 PM Re: Archiving Data [Re: skinsey]
Anonymous
Unregistered



But this will exactly the same with a database, the amount of data never decreases. The database will spend a lot of time re-index (moving the indextable
around) even if you add records to a table.

Anyone running FTS and get it working?

--
Jarl Groneng
jgroneng@online.no


29.12.2000 14:40:33, "Connelly, Michael R." wrote:

>**
>
>Something to be aware of with this archiving approach is that if you do FTS
>then you are simply moving the data to another form causing is to be
>re-indexed. Overall your server will always be working more on FTS
>re-indexes because the amount of data never decreases. We have implemented
>an archiving strategy where we export data yearly that is older than 3
>years. In some of our other systems where the need to keep the data, but not
>see it exists, we use a active link to set a flag no matter what the user
>searches on. We have an escalation process that "ages" the records, and a
>filter that sets the flag to true upon reaching a certain age.
>
> M i c h a e l R. C o n n e l l y
> The Johns Hopkins University Applied Physics Laboratory
> 11100 Johns Hopkins Road, Laurel, MD 20723
> Phone: 443 778-7323, Fax: 443 778-1093
> michael.connelly@jhuapl.edu
>
>
>-----Original Message-----
>From: Jarl Groneng [mailto:rapid@ONLINE.NO]
>Sent: December 29, 2000 12:31
>To: ARSLIST@LISTSERV.VISTAIT.COM
>Subject: Re: Archiving Data
>
>
>**
>
>Not detailed, but here is how we does it:
>
>Created a 100% indetical form (no workflow at all), set all fields to
>read-only. When a ticket is set to Closed, this record is moved over to the
>archive form. In
>the main form there is two field, listing the number of open and closed
>tickets. A button can be used to list all open or closed tickets.
>
>In our control-panel the users can search for ie entry-id, the mcaro search
>first in the mainform, if no hit then it search in the archiveform.
>
>--
>Jarl Groneng
>jgroneng@online.no
>
>
>29.12.2000 08:58:58, "Sprenger, Janie : CO IR" wrote:
>
>>**
>>
>>Does anyone have detailed instructions on how to archive data from a form
>>and still keep it accessible? Opinions and suggestions needed. Thanks
>>
>>Janie Sprenger
>>Remedy Administrator
>>Legacy Health System
>>Portland, OR
>>503-415-5826
>>
>>
>>
>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>





Top


Moderator:  Matt Reinfeldt