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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: archiving data
There is one approach that you didn't mention that I think is underutilized. You can partition the tables using the partitioning features of your db. The advantages to this include: - 1 form for archived and current data - can be managed from the ardb.cfg file (admin tool-> server info-> db tab) The drawbacks include: - you are limited by the capabilities of your db - the queries your system generates needs to be considerate of the partitions - e.g., you can still cause table scans against the entire data set - you need to also define clauses in the ardb.conf for the indexes that include the partitioned column, if applicable It's a little more involved to configure and set up, but the result is a method of archiving that is transparent to your users and workflow. All the tables, buttons, active links, etc. just work after your archiving solution is in place. Some reading material: MSSQL 2000 - http://msdn2.microsoft.com/en-us/library/aa902650(SQL.80).aspx MSSQL 2005 - http://blogs.msdn.com/mwories/archive/2005/06/24/table-partitioning-sample.aspx Since you are on sql server, this db capability did not really mature until version 2005. There were some rudimentary methods to achieve partitioning in 2000, but they were exactly that, and using those methods with Remedy would not be feasible. All supported releases of Oracle support partitioning as part of the create/alter table ddl. MSSQL 2005+ support partitioning as part of the create/alter table ddl. The ddl clauses are what you need to use the ardb.conf method of implementation/maintenance. Axton Grams On 4/24/07, Jorge Polo <[EMAIL PROTECTED]> wrote: ** 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"
Re: archiving data
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"
Re: archiving data
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"
Re: archiving data
Hello Pierre, I would be interested in the demo app if you don't mind. Best regards, Neel Gautam Accenture - Chicago Delivery Centre Office: 312-693-7279 Mobile: 630-440-6335 MSN: [EMAIL PROTECTED] AIM: neelgautam Core Values: Stewardship * Best People * Client Value Creation * One Global Network * Respect for the Individual * Integrity From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pierre Lafortune Sent: Wednesday, April 25, 2007 9:09 AM To: arslist@ARSLIST.ORG Subject: Re: archiving data 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___ __20060125___This posting was submitted with HTML in it___ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: archiving data
Hi List - anyone know if the 7.0 odbc driver supports joining tables? Thanks Chris Cook ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Remedy - Archiving Data
Hi Everyone Hoping to get some feedback to the following: We are looking into archiving our Incident Management data. We are currently running 7.5.1, but expect to upgrade by the end of the calendar year. The modules currently running are IM, CM, AM, SRM (not heavily yet, so many requests come through IM) , SLM. When I review the out of the box processes - I am not really seeing any advantages to the Remedy archive other than performance on searches within the data base itself. I thought the idea would be to not only improve performance but save on disk space as well.. Our rules must include the ability to restore records if they are deleted as part of this process, or if we do not delete them, have the ability to search and report off of the archive. Our retention rule is 3 years in an accessible, readable format. So.. just looking to hear back on what strategies others are or have used and how effective those strategies are! Any feedback would be great appreciated! Have a great Memorial day week-end! Thanks C * This e-mail and any files transmitted with it may contain confidential information and is intended solely for use by the individual to whom it is addressed. If you received this e-mail in error, please notify the sender, do not disclose its contents to others and delete it from your system. * ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Help on archiving data.
Hi all, Can you please let me know your suggestions on requirements 1 and 2? 1) Transfer records from a regular form to an archive form and delete records from the regular form. I don't want to use built-in remedy archive feature as it consumes lot of resources and takes long time to complete. 2) Transfer records from an archive table to a different database table and delete records from the archive table. The AR System database is oracle. Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Help on archiving data.
Hi all, Can you please let me know your suggestions/solutions on requirements 1 and 2? 1) Transfer records from a regular form to an archive form and delete records from the regular form. I don't want to use built-in remedy archive feature as it consumes lot of resources and takes long time to complete. 2) Transfer records from an archive table to a different database table and delete records from the archive table. The AR System database is oracle. Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Remedy - Archiving Data
Christine, We’re on also 7.5.01 and looking at an upgrade. I’ve used archive with the “Delete from Source” option on a couple of forms & not had any problem. However, when I tried the “Copy to Archive and Delete from Source” option, the Archive form generates the following error when searching for records: ARERR [313] Data types are not appropriate for relational operation Keep in mind the records do display but this error pops up every time moving through the results list or when clicking on the table on the Relationships tab. According to BMC, this is defect SW00400948. There’s no fix for this version as it’s fixed in later versions. You might want to check out your system & see if you get the same error. Maybe someone on the list can suggest a fix? Rebecca On Thu, May 23, 2013 at 10:55 AM, Christine Milton Hall < christine_milton_h...@pepperidgefarm.com> wrote: > ** > > Hi Everyone > > > > Hoping to get some feedback to the following: > > > > We are looking into archiving our Incident Management data. We are > currently running 7.5.1, but expect to upgrade by the end of the calendar > year. The modules currently running are IM, CM, AM, SRM (not heavily yet, > so many requests come through IM) , SLM. When I review the out of the box > processes – I am not really seeing any advantages to the Remedy archive > other than performance on searches within the data base itself. I thought > the idea would be to not only improve performance but save on disk space as > well.. > > > > Our rules must include the ability to restore records if they are deleted > as part of this process, or if we do not delete them, have the ability to > search and report off of the archive. Our retention rule is 3 years in an > accessible, readable format. > > > > So.. just looking to hear back on what strategies others are or have used > and how effective those strategies are! > > > > Any feedback would be great appreciated! Have a great Memorial day > week-end! > > > > Thanks > > C > > * > > > This e-mail and any files transmitted with it may contain confidential > information and is intended solely for use by the individual to whom it is > addressed. If you received this e-mail in error, please notify the sender, > do not disclose its contents to others and delete it from your system. > > * > > _ARSlist: "Where the Answers Are" and have been for 20 years_ -- Rebecca Boyd Application Administrator Wake Forest University ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Archiving Data in Remedy
Hello Listers, I am looking for best practices and ideas for the beginning of Remedy data archival. We have had Remedy here for almost a year and are beginning to look into data archival options. Can anyone share ideas or experiences? Thanks in Advance, ") Help Desk 6.0 Windows Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] DaVita Inc. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Help on archiving data.
For the first option the only solution from ARS, is to do it with escalations. But I presume that the consumption and time consuming will be higher. Another option is to do it at database level. It will go very fast. Just create a programmed task that do this job. The only you need is to process the time filed to know when a request is old enough to be transfered. If you are using Oracle, you can look at: http://theremedyforit.com/2012/02/oracle-epoch-converter-function-for-remedy/ About the second question, it's about the same, but you need to publish the table at your database, so ARS can access it through a view form or your programmed task can access it. Regards, Jose Huerta ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Help on archiving data.
Robin, I'm sure any method you use that is supported (through the application) will take just as long as the archive process built in, so your only option that I can think of that would be faster would be through DB directly, but doing that of course is not recommended or supported by BMC...so if you decide to go down that path, you go 'alone' from a support perspective. Regarding taking things out of Remedy DB into another DBthis of course steps outside of the Remedy world anyway...but as Jose suggested, you can do this directly at the DB as well. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Robin Sent: Tuesday, August 07, 2012 1:02 AM To: arslist@ARSLIST.ORG Subject: Help on archiving data. Hi all, Can you please let me know your suggestions on requirements 1 and 2? 1) Transfer records from a regular form to an archive form and delete records from the regular form. I don't want to use built-in remedy archive feature as it consumes lot of resources and takes long time to complete. 2) Transfer records from an archive table to a different database table and delete records from the archive table. The AR System database is oracle. Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Archiving Data in Remedy
Hi Jase, This is a 3-tier strategy I have often used. 1. One Active form where all active records are stored. Closed records will only stay herer for 1-3 months depending on the requirements you have. 2. One Report/History form where all closed records are immediately copied. The records stay there i.e. 13 months. 3. One Archive form where records are moved from the Report/History form after 13 months. The built in archiving has its pros and cons. I have many times used my rrrchive-tool which has the advantage of retaining the Entry-ID of the Active form. It is allways easier to manage a solution without "external" dependencies... Best Regards - Misi, RRR AB, http://www.rrr.se/sv/ > Hello Listers, > > I am looking for best practices and ideas for the beginning of Remedy > data archival. We have had Remedy here for almost a year and are > beginning to look into data archival options. > Can anyone share ideas or experiences? > > > Thanks in Advance, ") > > > Help Desk 6.0 > Windows > > > Jase Brandon > > Remedy Administration/Development > > Customer Support Systems Group > > Desk - (615) - 320-4494 > > Cell - (334) - 318-5426 > > [EMAIL PROTECTED] > > > > DaVita Inc. > > ___ > 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"
Re: Archiving Data in Remedy
Jase, I have seen company archives any closed ticket which is 18 months or older. Here in Alliance Bernstein, we use 24 months. People needs to report on up to 2 years of data, that's why we use 24months. Our Remedy system performance looks fine with 24months archiving. (knock wood) Jason Niu Sr. Remedy System Engineer Remedy System & Operation GETS - Enterprise Systems Management Email:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 135 W 50th Street, NYC,NY,10020 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jase Brandon Sent: Thursday, November 30, 2006 12:11 PM To: arslist@ARSLIST.ORG Subject: [ARSLIST] Archiving Data in Remedy ** Hello Listers, I am looking for best practices and ideas for the beginning of Remedy data archival. We have had Remedy here for almost a year and are beginning to look into data archival options. Can anyone share ideas or experiences? Thanks in Advance, ") Help Desk 6.0 Windows Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] DaVita Inc. __20060125___This posting was submitted with HTML in it___ - The information contained in this transmission may be privileged and confidential and is intended only for the use of the person(s) named above. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies of the original message. Please note that we do not accept account orders and/or instructions by e-mail, and therefore will not be responsible for carrying out such orders and/or instructions. If you, as the intended recipient of this message, the purpose of which is to inform and update our clients, prospects and consultants of developments relating to our services and products, would not like to receive further e-mail correspondence from the sender, please "reply" to the sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New York, NY 10105. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
Hi Misi, Thanks for your quick response! Have you used the built in archiving feature in Remedy Help Desk 6.0? Can you tell me the pros and cons of the built in archiving? We recently bought rrr's license utility tool, would there be an additional cost for using the rrr archiving tool? Can you tell me more about the rrrchive tool? Thanks in advance, :) Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky Sent: Thursday, November 30, 2006 12:03 PM To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy Hi Jase, This is a 3-tier strategy I have often used. 1. One Active form where all active records are stored. Closed records will only stay herer for 1-3 months depending on the requirements you have. 2. One Report/History form where all closed records are immediately copied. The records stay there i.e. 13 months. 3. One Archive form where records are moved from the Report/History form after 13 months. The built in archiving has its pros and cons. I have many times used my rrrchive-tool which has the advantage of retaining the Entry-ID of the Active form. It is allways easier to manage a solution without "external" dependencies... Best Regards - Misi, RRR AB, http://www.rrr.se/sv/ > Hello Listers, > > I am looking for best practices and ideas for the beginning of Remedy > data archival. We have had Remedy here for almost a year and are > beginning to look into data archival options. > Can anyone share ideas or experiences? > > > Thanks in Advance, ") > > > Help Desk 6.0 > Windows > > > Jase Brandon > > Remedy Administration/Development > > Customer Support Systems Group > > Desk - (615) - 320-4494 > > Cell - (334) - 318-5426 > > [EMAIL PROTECTED] > > > > DaVita Inc. > > __ > _ 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" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
One con of the ARS 6.0 archiving is that once you turn it on, you can't add fields to the form being archived. there's a current bug logged and I've been waiting for a fix for about 2 months. I'd advise against that path. - Chris Jase Brandon <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" 11/30/2006 03:13 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: Archiving Data in Remedy Hi Misi, Thanks for your quick response! Have you used the built in archiving feature in Remedy Help Desk 6.0? Can you tell me the pros and cons of the built in archiving? We recently bought rrr's license utility tool, would there be an additional cost for using the rrr archiving tool? Can you tell me more about the rrrchive tool? Thanks in advance, :) Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky Sent: Thursday, November 30, 2006 12:03 PM To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy Hi Jase, This is a 3-tier strategy I have often used. 1. One Active form where all active records are stored. Closed records will only stay herer for 1-3 months depending on the requirements you have. 2. One Report/History form where all closed records are immediately copied. The records stay there i.e. 13 months. 3. One Archive form where records are moved from the Report/History form after 13 months. The built in archiving has its pros and cons. I have many times used my rrrchive-tool which has the advantage of retaining the Entry-ID of the Active form. It is allways easier to manage a solution without "external" dependencies... Best Regards - Misi, RRR AB, http://www.rrr.se/sv/ > Hello Listers, > > I am looking for best practices and ideas for the beginning of Remedy > data archival. We have had Remedy here for almost a year and are > beginning to look into data archival options. > Can anyone share ideas or experiences? > > > Thanks in Advance, ") > > > Help Desk 6.0 > Windows > > > Jase Brandon > > Remedy Administration/Development > > Customer Support Systems Group > > Desk - (615) - 320-4494 > > Cell - (334) - 318-5426 > > [EMAIL PROTECTED] > > > > DaVita Inc. > > __ > _ 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" ___ 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"
Re: Archiving Data in Remedy
Hi Jase, The pros with the built in archiving is that it is built in, and you can consequently access it fully through ARAdmin. The cons are that: - it is not that flexible - it supports only one tier of archiving (the last time I tried it) - it creates a new field to contain the original Request ID and concequently creats a new Request ID for the archived record - and we have heard of some bugs You can sign up for support for rrrChive, if you need a supported product, or want to sponsor future development ;-) Unfortunately, there has been very few problems with rrrChive... If you use rrrChive for Archiving records, you just have to look out for a situation where you try to archive 1000 records simultaneously by starting 1000 parallel rrrChive-processes. The usual pitfall is an escalation that closes 1000 records. In the past we have kept the newer versions for support customers. We have decided to release the version 6.3 and 7.0 to everyone. I will do so in a couple of days, so look out for that! Best Regards - Misi, RRR AB, http://www.rrr.se/sv/ > Hi Misi, > Thanks for your quick response! Have you used the built in archiving > feature in Remedy Help Desk 6.0? > > Can you tell me the pros and cons of the built in archiving? > > We recently bought rrr's license utility tool, would there be an > additional cost for using the rrr archiving tool? > > Can you tell me more about the rrrchive tool? > > Thanks in advance, :) > > Jase Brandon > Remedy Administration/Development > Customer Support Systems Group > Desk - (615) - 320-4494 > Cell - (334) - 318-5426 > [EMAIL PROTECTED] > > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky > Sent: Thursday, November 30, 2006 12:03 PM > To: arslist@ARSLIST.ORG > Subject: Re: Archiving Data in Remedy > > Hi Jase, > > This is a 3-tier strategy I have often used. > > 1. One Active form where all active records are stored. Closed records > will only stay herer for 1-3 months depending on the requirements you > have. > > 2. One Report/History form where all closed records are immediately > copied. The records stay there i.e. 13 months. > > 3. One Archive form where records are moved from the Report/History form > after 13 months. > > The built in archiving has its pros and cons. I have many times used my > rrrchive-tool which has the advantage of retaining the Entry-ID of the > Active form. It is allways easier to manage a solution without > "external" > dependencies... > > Best Regards - Misi, RRR AB, http://www.rrr.se/sv/ > >> Hello Listers, >> >> I am looking for best practices and ideas for the beginning of Remedy >> data archival. We have had Remedy here for almost a year and are >> beginning to look into data archival options. >> Can anyone share ideas or experiences? >> >> >> Thanks in Advance, ") >> >> >> Help Desk 6.0 >> Windows >> >> >> Jase Brandon >> >> Remedy Administration/Development >> >> Customer Support Systems Group >> >> Desk - (615) - 320-4494 >> >> Cell - (334) - 318-5426 >> >> [EMAIL PROTECTED] >> >> >> >> DaVita Inc. >> >> __ >> _ 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" > > ___ > 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"
Re: Archiving Data in Remedy
Hi Jase, We have tried to use the built in archiving on numerous occasions and it let us down badly. From the archive form not being accessible to adding of fields etc. These can lead to the loss of data. What we did was use a similar approach as Remedy but build our own. We took the original form and copied it, removed all the unnecessary fields like page fields, table fields and buttons, changed the permissions to public on all the fields that remained. Form permissions are reserved for admins or a specific group. We then have 2 fields that are used to control the copy of the data (which could be done by either push or DSO, depending on what fits our needs). These same fields are applied to the archive form. The one field is used as a trigger which is stepped through stages. An escalation selects the records and marks this field ready for archive. This triggers a copy to the archive form. From the archive form an escalation checks the staging field and sets the original form as copied and an escalation takes care of the delete from the original form. I forgot, we had to create another field to house the original ID (same as Remedy). Trust this gives you an idea. Regards, Basil Webster Remedy Developer Siemens Business Services (Pty) Ltd * E-Mail: [EMAIL PROTECTED] * Tel: +27 11 652 7523 * Fax: +27 11 652-7501 * Mobile: +27 82 452 9389 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jase Brandon Sent: 30 November 2006 19:11 To: arslist@ARSLIST.ORG Subject: Archiving Data in Remedy Hello Listers, I am looking for best practices and ideas for the beginning of Remedy data archival. We have had Remedy here for almost a year and are beginning to look into data archival options. Can anyone share ideas or experiences? Thanks in Advance, ") Help Desk 6.0 Windows Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] DaVita Inc. __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
Hi, we have done exactly the same, and it has been up and running i prod för about 3-4 years, we archive request which have been in staus closed for 13 months, 500 every night including attachments, escalations and push field action, works fine. /L ars -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Webster, Basil Sent: Friday, December 01, 2006 11:03 AM To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy ** Hi Jase, We have tried to use the built in archiving on numerous occasions and it let us down badly. From the archive form not being accessible to adding of fields etc. These can lead to the loss of data. What we did was use a similar approach as Remedy but build our own. We took the original form and copied it, removed all the unnecessary fields like page fields, table fields and buttons, changed the permissions to public on all the fields that remained. Form permissions are reserved for admins or a specific group. We then have 2 fields that are used to control the copy of the data (which could be done by either push or DSO, depending on what fits our needs). These same fields are applied to the archive form. The one field is used as a trigger which is stepped through stages. An escalation selects the records and marks this field ready for archive. This triggers a copy to the archive form. From the archive form an escalation checks the staging field and sets the original form as copied and an escalation takes care of the delete from the original form. I forgot, we had to create another field to house the original ID (same as Remedy). Trust this gives you an idea. Regards, Basil Webster Remedy Developer Siemens Business Services (Pty) Ltd * E-Mail: [EMAIL PROTECTED] * Tel: +27 11 652 7523 * Fax: +27 11 652-7501 * Mobile: +27 82 452 9389 _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jase Brandon Sent: 30 November 2006 19:11 To: arslist@ARSLIST.ORG Subject: Archiving Data in Remedy Hello Listers, I am looking for best practices and ideas for the beginning of Remedy data archival. We have had Remedy here for almost a year and are beginning to look into data archival options. Can anyone share ideas or experiences? Thanks in Advance, ") Help Desk 6.0 Windows Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] DaVita Inc. __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
I haven't seen discussion about disk space and indexes relative to archival, so thought I'd add it as a consideration. In most databases, such as Oracle and MS SQL, records aren't actually deleted, but rather are flagged for delete. Usually some "other activity" is used to reclaim disk space from deleted records and reorganize indexes/index pages. "Other activity" in the case of Oracle 9i and earlier is to "drop table" and re-add, although I've read that export/import can be used as well. Some databases have a "reorg" or "compact" utility for this purpose. For low-volume or low-access tables, this may be insignificant. It can be performance-impacting for larger tables, though, especially if there's a high record turnover due to archive. We have a table with nearly a million records, for example. We add roughly 80K records per month and archive 60K (and growing - to 80K eventually). Our application that reads and writes to the table became noticeably slower over time, then improved dramatically after table delete/re-import. May or may not be an issue, but it's worth thinking about table and application behavior and performance. Mike White Office: 813-978-2192 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] TENFALL.COM To: arslist@ARSLIST.ORG Sent by: "Action cc: Request System Subject: Re: Archiving Data in Remedy discussion list(ARSList)" 12/01/2006 05:09 Please respond to arslist ** Hi, we have done exactly the same, and it has been up and running i prod för about 3-4 years, we archive request which have been in staus closed for 13 months, 500 every night including attachments, escalations and push field action, works fine. /L ars -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Webster, Basil Sent: Friday, December 01, 2006 11:03 AM To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy ** Hi Jase, We have tried to use the built in archiving on numerous occasions and it let us down badly. From the archive form not being accessible to adding of fields etc. These can lead to the loss of data. What we did was use a similar approach as Remedy but build our own. We took the original form and copied it, removed all the unnecessary fields like page fields, table fields and buttons, changed the permissions to public on all the fields that remained. Form permissions are reserved for admins or a specific group. We then have 2 fields that are used to control the copy of the data (which could be done by either push or DSO, depending on what fits our needs). These same fields are applied to the archive form. The one field is used as a trigger which is stepped through stages. An escalation selects the records and marks this field ready for archive. This triggers a copy to the archive form. From the archive form an escalation checks the staging field and sets the original form as copied and an escalation takes care of the delete from the original form. I forgot, we had to create another field to house the original ID (same as Remedy). Trust this gives you an idea. Regards, Basil Webster Remedy Developer Siemens Business Services (Pty) Ltd * E-Mail: [EMAIL PROTECTED] ( Tel: +27 11 652 7523 Ê Fax: +27 11 652-7501 ) Mobile: +27 82 452 9389 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jase Brandon Sent: 30 November 2006 19:11 To: arslist@ARSLIST.ORG Subject: Archiving Data in Remedy Hello Listers, I am looking for best practices and ideas for the beginning of Remedy data archival. We have had Remedy here for almost a year and are beginning to look into data archival options. Can anyone share ideas or experiences? Thanks in Advan
Re: Archiving Data in Remedy
To me, the biggest pitfall is that there is only one thread for escalations. This is problematic if you use escalations for other processes (such as notifications, record clean-up/deletion, etc) that fight for an open escalation thread. In this case, proper table indexing, archiving/record deletion time staggering and database performance tweaks will all help alleviate some pain. Thank you, Richard Crosby Starbucks Coffee Company | Information Technology | [EMAIL PROTECTED] | (206) 318-4614 One day your ship will come in, but you'll be at the airport. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
There is a big bug in ARS 6.0.1 archiving. As soon as you enable archiving on a form and the archive form is generated by ARS, all the default values on all fields of the original form are blanked out permanently !!! I think it was fixed in Patch 1491... Regards, Murtuza. From: Richard Crosby <[EMAIL PROTECTED]> Reply-To: arslist@ARSLIST.ORG To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy Date: Fri, 1 Dec 2006 08:07:53 -0800 To me, the biggest pitfall is that there is only one thread for escalations. This is problematic if you use escalations for other processes (such as notifications, record clean-up/deletion, etc) that fight for an open escalation thread. In this case, proper table indexing, archiving/record deletion time staggering and database performance tweaks will all help alleviate some pain. Thank you, Richard Crosby Starbucks Coffee Company | Information Technology | [EMAIL PROTECTED] | (206) 318-4614 One day your ship will come in, but you'll be at the airport. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Archiving Data in Remedy
Much to our surprise that bug also exists in ARS 6.3 at least up to patch 13. We're now on patch 18. Somewhere between 13 and 18 it was fixed. Michelle -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of msb * Sent: Monday, December 04, 2006 12:13 AM To: arslist@ARSLIST.ORG Subject: Re: Archiving Data in Remedy There is a big bug in ARS 6.0.1 archiving. As soon as you enable archiving on a form and the archive form is generated by ARS, all the default values on all fields of the original form are blanked out permanently !!! I think it was fixed in Patch 1491... Regards, Murtuza. >From: Richard Crosby <[EMAIL PROTECTED]> >Reply-To: arslist@ARSLIST.ORG >To: arslist@ARSLIST.ORG >Subject: Re: Archiving Data in Remedy >Date: Fri, 1 Dec 2006 08:07:53 -0800 > >To me, the biggest pitfall is that there is only one thread for >escalations. This is problematic if you use escalations for other >processes (such as notifications, record clean-up/deletion, etc) that >fight for an open escalation thread. In this case, proper table >indexing, archiving/record deletion time staggering and database >performance tweaks will all help alleviate some pain. > > > >Thank you, > > > >Richard Crosby > >Starbucks Coffee Company | Information Technology > >| [EMAIL PROTECTED] | (206) 318-4614 > > > >One day your ship will come in, but you'll be at the airport. > > > > >___ >UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where >the Answers Are" _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ 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"
Re: Archiving Data in Remedy
H. We're running 6.0.1, patch 1497 and didn't have this issue. I just
double-checked our default values - none were disturbed. It's an active
archive that's been running for months.
We have other archive issues, but don't seem to have this one.
To paraphrase (for clarity) - you're saying that if you enable archive on a
form, Remedy removes default values on the main/source form.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
"Lucero, Michelle
- IST contractor"To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in
Remedy
Sent by: "Action
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
12/04/2006 09:45
Please respond to
arslist
Much to our surprise that bug also exists in ARS 6.3 at least up to
patch 13. We're now on patch 18. Somewhere between 13 and 18 it was
fixed.
Michelle
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of msb *
Sent: Monday, December 04, 2006 12:13 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
There is a big bug in ARS 6.0.1 archiving.
As soon as you enable archiving on a form and the archive form is
generated
by ARS, all the default values on all fields of the original form are
blanked out permanently !!!
I think it was fixed in Patch 1491...
Regards,
Murtuza.
>From: Richard Crosby <[EMAIL PROTECTED]>
>Reply-To: arslist@ARSLIST.ORG
>To: arslist@ARSLIST.ORG
>Subject: Re: Archiving Data in Remedy
>Date: Fri, 1 Dec 2006 08:07:53 -0800
>
>To me, the biggest pitfall is that there is only one thread for
>escalations. This is problematic if you use escalations for other
>processes (such as notifications, record clean-up/deletion, etc) that
>fight for an open escalation thread. In this case, proper table
>indexing, archiving/record deletion time staggering and database
>performance tweaks will all help alleviate some pain.
>
>
>
>Thank you,
>
>
>
>Richard Crosby
>
>Starbucks Coffee Company | Information Technology
>
>| [EMAIL PROTECTED] | (206) 318-4614
>
>
>
>One day your ship will come in, but you'll be at the airport.
>
>
>
>
>___
>UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where
>the Answers Are"
_
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
___
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"
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Archiving Data in Remedy
YES!
I had to test it, just to make sure I wasn't imagining things. I
believe there are about 60+ default values on the HPD:HelpDesk form.
After turning on archiving it removed all but four of them on the
original form.
I repeated the same test, by reimporting a "good copy" of the form back
into the dev environment. Turned on archiving, and it happened again.
Let me see if I can find the bug number
Found it. It was fixed and listed in the Release Notes for ARS Server
6.3 patch 17.
SW00223771 Copy to archive drops all default values for fields
except for the system field.
Hope that helps,
Michelle
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mike White
Sent: Monday, December 04, 2006 9:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
H. We're running 6.0.1, patch 1497 and didn't have this issue. I
just
double-checked our default values - none were disturbed. It's an active
archive that's been running for months.
We have other archive issues, but don't seem to have this one.
To paraphrase (for clarity) - you're saying that if you enable archive
on a
form, Remedy removes default values on the main/source form.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
"Lucero, Michelle
- IST contractor"To:
arslist@ARSLIST.ORG
Subject: Re: Archiving
Data in Remedy
Sent by: "Action
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
12/04/2006 09:45
Please respond to
arslist
Much to our surprise that bug also exists in ARS 6.3 at least up to
patch 13. We're now on patch 18. Somewhere between 13 and 18 it was
fixed.
Michelle
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of msb *
Sent: Monday, December 04, 2006 12:13 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
There is a big bug in ARS 6.0.1 archiving.
As soon as you enable archiving on a form and the archive form is
generated
by ARS, all the default values on all fields of the original form are
blanked out permanently !!!
I think it was fixed in Patch 1491...
Regards,
Murtuza.
>From: Richard Crosby <[EMAIL PROTECTED]>
>Reply-To: arslist@ARSLIST.ORG
>To: arslist@ARSLIST.ORG
>Subject: Re: Archiving Data in Remedy
>Date: Fri, 1 Dec 2006 08:07:53 -0800
>
>To me, the biggest pitfall is that there is only one thread for
>escalations. This is problematic if you use escalations for other
>processes (such as notifications, record clean-up/deletion, etc) that
>fight for an open escalation thread. In this case, proper table
>indexing, archiving/record deletion time staggering and database
>performance tweaks will all help alleviate some pain.
>
>
>
>Thank you,
>
>
>
>Richard Crosby
>
>Starbucks Coffee Company | Information Technology
>
>| [EMAIL PROTECTED] | (206) 318-4614
>
>
>
>One day your ship will come in, but you'll be at the airport.
>
>
>
>
>___
>UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where
>the Answers Are"
_
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
___
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"
___
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"
Re: Archiving Data in Remedy
I don't remember right but it was fixed in Patch 1497 for 6.0.1 or the one
before it.
From: Mike White <[EMAIL PROTECTED]>
Reply-To: arslist@ARSLIST.ORG
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
Date: Mon, 4 Dec 2006 10:08:13 -0500
H. We're running 6.0.1, patch 1497 and didn't have this issue. I just
double-checked our default values - none were disturbed. It's an active
archive that's been running for months.
We have other archive issues, but don't seem to have this one.
To paraphrase (for clarity) - you're saying that if you enable archive on a
form, Remedy removes default values on the main/source form.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
"Lucero, Michelle
- IST contractor"To:
arslist@ARSLIST.ORG
MKCORP.COM> Subject: Re: Archiving
Data in Remedy
Sent by: "Action
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
12/04/2006 09:45
Please respond to
arslist
Much to our surprise that bug also exists in ARS 6.3 at least up to
patch 13. We're now on patch 18. Somewhere between 13 and 18 it was
fixed.
Michelle
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of msb *
Sent: Monday, December 04, 2006 12:13 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
There is a big bug in ARS 6.0.1 archiving.
As soon as you enable archiving on a form and the archive form is
generated
by ARS, all the default values on all fields of the original form are
blanked out permanently !!!
I think it was fixed in Patch 1491...
Regards,
Murtuza.
>From: Richard Crosby <[EMAIL PROTECTED]>
>Reply-To: arslist@ARSLIST.ORG
>To: arslist@ARSLIST.ORG
>Subject: Re: Archiving Data in Remedy
>Date: Fri, 1 Dec 2006 08:07:53 -0800
>
>To me, the biggest pitfall is that there is only one thread for
>escalations. This is problematic if you use escalations for other
>processes (such as notifications, record clean-up/deletion, etc) that
>fight for an open escalation thread. In this case, proper table
>indexing, archiving/record deletion time staggering and database
>performance tweaks will all help alleviate some pain.
>
>
>
>Thank you,
>
>
>
>Richard Crosby
>
>Starbucks Coffee Company | Information Technology
>
>| [EMAIL PROTECTED] | (206) 318-4614
>
>
>
>One day your ship will come in, but you'll be at the airport.
>
>
>
>
>___
>UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where
>the Answers Are"
_
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
___
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"
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
Re: Archiving Data in Remedy
Mike,
For Oracle 9i, 10g you can move a table online, which has the effect of
reorganizing the table.
Since this operation is "online", the table is still available, since a copy of
it is done in memory, and this copy is the one accessed, while the reorging
occurs.
You can also rebuild indexes online. So at least with Oracle, you definitely do
not need to export data, remove the table, recreate it, and import the data.
10g also has a shrink segment feature that is faster than the table online
reorg, so that option seems better for very large tables
BTW, this online reorging of tables and rebuilding indexes has been available
since Oracle 8i I believe
Guillaume
From: Mike White
Sent: Fri 12/01/06 8:59 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
I haven't seen discussion about disk space and indexes relative to
archival, so thought I'd add it as a consideration. In most databases,
such as Oracle and MS SQL, records aren't actually deleted, but rather are
flagged for delete. Usually some "other activity" is used to reclaim disk
space from deleted records and reorganize indexes/index pages. "Other
activity" in the case of Oracle 9i and earlier is to "drop table" and
re-add, although I've read that export/import can be used as well. Some
databases have a "reorg" or "compact" utility for this purpose.
For low-volume or low-access tables, this may be insignificant. It can be
performance-impacting for larger tables, though, especially if there's a
high record turnover due to archive. We have a table with nearly a million
records, for example. We add roughly 80K records per month and archive 60K
(and growing - to 80K eventually). Our application that reads and writes
to the table became noticeably slower over time, then improved dramatically
after table delete/re-import.
May or may not be an issue, but it's worth thinking about table and
application behavior and performance.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
TENFALL.COM To:
arslist@ARSLIST.ORG
Sent by: "Action cc:
Request System Subject: Re: Archiving Data
in Remedy
discussion
list(ARSList)"
12/01/2006 05:09
Please respond to
arslist
**
Hi, we have done exactly the same, and it has been up and running i prod
för about 3-4 years, we archive request which have been in staus closed for
13 months, 500 every night including attachments, escalations and push
field action, works fine. /L ars
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Webster, Basil
Sent: Friday, December 01, 2006 11:03 AM
To: arslist@ARSLIST.ORG
Subject: Re: Archiving Data in Remedy
**
Hi Jase,
We have tried to use the built in archiving on numerous occasions and
it let us down badly. From the archive form not being accessible to
adding of fields etc. These can lead to the loss of data.
What we did was use a similar approach as Remedy but build our own.
We took the original form and copied it, removed all the unnecessary
Re: EXTERNAL: Help on archiving data.
Robin, Both of these could be handled by RRR|Chive. www.rrr.se Misi's tools are very straight forward. Thank you, --- John J. Reiser Remedy Developer/Administrator Senior Software Development Analyst Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Robin Sent: Tuesday, August 07, 2012 3:07 AM To: arslist@ARSLIST.ORG Subject: EXTERNAL: Help on archiving data. Hi all, Can you please let me know your suggestions/solutions on requirements 1 and 2? 1) Transfer records from a regular form to an archive form and delete records from the regular form. I don't want to use built-in remedy archive feature as it consumes lot of resources and takes long time to complete. 2) Transfer records from an archive table to a different database table and delete records from the archive table. The AR System database is oracle. Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Hi, RRR|Chive has the ability to MOVE things, which is good when you do archiving. If the forms are identical, it is very easy, and you can retain the original Request ID, which the built in archiving does not support. You can also use RRR|Chive to archive things to ARX-files. If you then use RRR|ArxToHTML, you get a very simple way of accessing your old data from a web server or a file share. Here is a sample database dump done with RRR|Chive and RRR|ArxToHTML of a newly installed ITSM 7.6.04 Stack Installer: http://rrr.se/itsmdoc/itsm764arxhtml/ This sample rrrchive config will archive between two forms after 3 months: source_server = myserver source_user = Demo source_password = source_form = HPD:Help Desk target_server = myserver target_form = HPD:Help Desk Archive qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 3*30*24*60*60 transfertype= MOVE logfile = AUTO progressbar = YES This sample rrrchive config will archive to ARX-files after 6 months: source_server = myserver source_user = Demo source_password = source_form = HPD:Help Desk Archive target_dir = C:\archive target_form = HPD:Help Desk Archive qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 6*30*24*60*60 transfertype= MOVE logfile = AUTO progressbar = YES This RRR|ArxToHTML call will create HTML pages based on an ARX-file and a DEF-file with the form definition: rrrArxToHTML.pl -suppressnull -d "c:\archivehtml\schema.def" -a "c:\archive\HPD_Help_Desk_Archive.arx" -t "c:\archivehtml\html" ADV: If you want a supported solution, you can always sign up for support on RRR|Chive, which is otherwise free to use. Just ask for a quote. Best Regards - Misi, RRR AB, http://rrr.se > Robin, > Both of these could be handled by RRR|Chive. > www.rrr.se > > Misi's tools are very straight forward. > > Thank you, > --- > John J. Reiser > Remedy Developer/Administrator > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me > > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Robin > Sent: Tuesday, August 07, 2012 3:07 AM > To: arslist@ARSLIST.ORG > Subject: EXTERNAL: Help on archiving data. > > Hi all, > > Can you please let me know your suggestions/solutions on requirements 1 > and 2? > > 1) Transfer records from a regular form to an archive form and delete > records from the regular form. I don't want to use built-in remedy archive > feature as it consumes lot of resources and takes long time to complete. > > 2) Transfer records from an archive table to a different database table > and delete records from the archive table. > > The AR System database is oracle. > > > Regards > Robin > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
In my last engagement I built a simple batch file to call RRR|Chive with parameters and then used the Windows scheduler to run monthly record archiving for anything older than 36 months to the read-only archive copy of the form (yes the business wanted to keep three years' worth of tickets in the live form). The batch file ran in the middle of the night (corporate office time) when Remedy activity was at its slowest so the performance impact was minimal. One caveat is that it was only moving less than 10K records each month. -Rick -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky Sent: Tuesday, August 07, 2012 7:01 AM To: arslist@ARSLIST.ORG Subject: Re: EXTERNAL: Help on archiving data. Hi, RRR|Chive has the ability to MOVE things, which is good when you do archiving. If the forms are identical, it is very easy, and you can retain the original Request ID, which the built in archiving does not support. You can also use RRR|Chive to archive things to ARX-files. If you then use RRR|ArxToHTML, you get a very simple way of accessing your old data from RRR|a web server or a file share. Here is a sample database dump done with RRR|Chive and RRR|ArxToHTML of a newly installed ITSM 7.6.04 Stack Installer: http://rrr.se/itsmdoc/itsm764arxhtml/ This sample rrrchive config will archive between two forms after 3 months: source_server = myserver source_user = Demo source_password = source_form = HPD:Help Desk target_server = myserver target_form = HPD:Help Desk Archive qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 3*30*24*60*60 transfertype= MOVE logfile = AUTO progressbar = YES This sample rrrchive config will archive to ARX-files after 6 months: source_server = myserver source_user = Demo source_password = source_form = HPD:Help Desk Archive target_dir = C:\archive target_form = HPD:Help Desk Archive qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 6*30*24*60*60 transfertype= MOVE logfile = AUTO progressbar = YES This RRR|ArxToHTML call will create HTML pages based on an ARX-file and a DEF-file with the form definition: rrrArxToHTML.pl -suppressnull -d "c:\archivehtml\schema.def" -a "c:\archive\HPD_Help_Desk_Archive.arx" -t "c:\archivehtml\html" ADV: If you want a supported solution, you can always sign up for support on RRR|Chive, which is otherwise free to use. Just ask for a quote. Best Regards - Misi, RRR AB, http://rrr.se > Robin, > Both of these could be handled by RRR|Chive. > www.rrr.se > > Misi's tools are very straight forward. > > Thank you, > --- > John J. Reiser > Remedy Developer/Administrator > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - > paraphrased by me > > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Robin > Sent: Tuesday, August 07, 2012 3:07 AM > To: arslist@ARSLIST.ORG > Subject: EXTERNAL: Help on archiving data. > > Hi all, > > Can you please let me know your suggestions/solutions on requirements > 1 and 2? > > 1) Transfer records from a regular form to an archive form and delete > records from the regular form. I don't want to use built-in remedy > archive feature as it consumes lot of resources and takes long time to > complete. > > 2) Transfer records from an archive table to a different database > table and delete records from the archive table. > > The AR System database is oracle. > > > Regards > Robin > > __ > _ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > __ > _ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Hi Rick, Can you elaborate on the "caveat"? There should be no 10K limit to the number of records RRR|Chive can move in a single run. And why not run it every night. This would minimize impact even further, as fewer records will be deleted each run. The technical limit of the 32-bit Windows version of RRR|Chive, when moving records is somewhere around 20M records per run. Make sure to use the splitsearch=YES parameter to avoid tablescans. Best Regards - Misi, RRR AB, http://rrr.se > In my last engagement I built a simple batch file to call RRR|Chive with > parameters and then used the Windows scheduler to run monthly record > archiving for anything older than 36 months to the read-only archive copy > of the form (yes the business wanted to keep three years' worth of tickets > in the live form). The batch file ran in the middle of the night > (corporate office time) when Remedy activity was at its slowest so the > performance impact was minimal. One caveat is that it was only moving less > than 10K records each month. > > -Rick > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky > Sent: Tuesday, August 07, 2012 7:01 AM > To: arslist@ARSLIST.ORG > Subject: Re: EXTERNAL: Help on archiving data. > > Hi, > > RRR|Chive has the ability to MOVE things, which is good when you do > archiving. If the forms are identical, it is very easy, and you can retain > the original Request ID, which the built in archiving does not support. > > You can also use RRR|Chive to archive things to ARX-files. If you then use > RRR|ArxToHTML, you get a very simple way of accessing your old data from > RRR|a > web server or a file share. > > Here is a sample database dump done with RRR|Chive and RRR|ArxToHTML of a > newly installed ITSM 7.6.04 Stack Installer: > http://rrr.se/itsmdoc/itsm764arxhtml/ > > This sample rrrchive config will archive between two forms after 3 months: > source_server = myserver > source_user = Demo > source_password = > source_form = HPD:Help Desk > target_server = myserver > target_form = HPD:Help Desk Archive > qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 3*30*24*60*60 > transfertype= MOVE > logfile = AUTO > progressbar = YES > > This sample rrrchive config will archive to ARX-files after 6 months: > source_server = myserver > source_user = Demo > source_password = > source_form = HPD:Help Desk Archive > target_dir = C:\archive > target_form = HPD:Help Desk Archive > qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 6*30*24*60*60 > transfertype= MOVE > logfile = AUTO > progressbar = YES > > This RRR|ArxToHTML call will create HTML pages based on an ARX-file and a > DEF-file with the form definition: > rrrArxToHTML.pl -suppressnull -d "c:\archivehtml\schema.def" -a > "c:\archive\HPD_Help_Desk_Archive.arx" -t "c:\archivehtml\html" > > ADV: If you want a supported solution, you can always sign up for support > on RRR|Chive, which is otherwise free to use. Just ask for a quote. > > Best Regards - Misi, RRR AB, http://rrr.se > >> Robin, >> Both of these could be handled by RRR|Chive. >> www.rrr.se >> >> Misi's tools are very straight forward. >> >> Thank you, >> --- >> John J. Reiser >> Remedy Developer/Administrator >> Senior Software Development Analyst >> Lockheed Martin - MS2 >> The star that burns twice as bright burns half as long. >> Pay close attention and be illuminated by its brilliance. - >> paraphrased by me >> >> >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arslist@ARSLIST.ORG] On Behalf Of Robin >> Sent: Tuesday, August 07, 2012 3:07 AM >> To: arslist@ARSLIST.ORG >> Subject: EXTERNAL: Help on archiving data. >> >> Hi all, >> >> Can you please let me know your suggestions/solutions on requirements >> 1 and 2? >> >> 1) Transfer records from a regular form to an archive form and delete >> records from the regular form. I don't want to use built-in remedy >> archive feature as it consumes lot of resources and takes long time to >> complete. >> >> 2) Transfer records from an archive table to a different database >> table and delete records from the archive table. >> >> The AR System database is oracle. >> >> >> Regards >> Robin >> >> _
Re: EXTERNAL: Help on archiving data.
Sorry about that, what I meant was that we weren't moving what I considered to be a large number of records since we didn't have a very busy help desk. If you had say over 100K records to move then that might cause other processes on the server to take a performance hit. I might even be remembering incorrectly, I might have scheduled it for every night as that does make much more sense. It has been several years since I even looked at that job and I've moved on to another engagement recently so I can't go back to check. In any case it was definitely a set & forget for me, it worked flawlessly to move the records over and retain request ID numbers as advertised. -Rick -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky Sent: Tuesday, August 07, 2012 8:44 AM To: arslist@ARSLIST.ORG Subject: Re: EXTERNAL: Help on archiving data. Hi Rick, Can you elaborate on the "caveat"? There should be no 10K limit to the number of records RRR|Chive can move in a single run. And why not run it every night. This would minimize impact even further, as fewer records will be deleted each run. The technical limit of the 32-bit Windows version of RRR|Chive, when moving records is somewhere around 20M records per run. Make sure to use the splitsearch=YES parameter to avoid tablescans. Best Regards - Misi, RRR AB, http://rrr.se > In my last engagement I built a simple batch file to call RRR|Chive > with parameters and then used the Windows scheduler to run monthly > record archiving for anything older than 36 months to the read-only > archive copy of the form (yes the business wanted to keep three years' > worth of tickets in the live form). The batch file ran in the middle > of the night (corporate office time) when Remedy activity was at its > slowest so the performance impact was minimal. One caveat is that it > was only moving less than 10K records each month. > > -Rick > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky > Sent: Tuesday, August 07, 2012 7:01 AM > To: arslist@ARSLIST.ORG > Subject: Re: EXTERNAL: Help on archiving data. > > Hi, > > RRR|Chive has the ability to MOVE things, which is good when you do > archiving. If the forms are identical, it is very easy, and you can > retain the original Request ID, which the built in archiving does not > support. > > You can also use RRR|Chive to archive things to ARX-files. If you then > use > RRR|ArxToHTML, you get a very simple way of accessing your old data > RRR|from a > web server or a file share. > > Here is a sample database dump done with RRR|Chive and RRR|ArxToHTML > of a newly installed ITSM 7.6.04 Stack Installer: > http://rrr.se/itsmdoc/itsm764arxhtml/ > > This sample rrrchive config will archive between two forms after 3 months: > source_server = myserver > source_user = Demo > source_password = > source_form = HPD:Help Desk > target_server = myserver > target_form = HPD:Help Desk Archive > qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 3*30*24*60*60 > transfertype= MOVE > logfile = AUTO > progressbar = YES > > This sample rrrchive config will archive to ARX-files after 6 months: > source_server = myserver > source_user = Demo > source_password = > source_form = HPD:Help Desk Archive > target_dir = C:\archive > target_form = HPD:Help Desk Archive > qual= '7' = "Closed" AND '6' < $TIMESTAMP$ - 6*30*24*60*60 > transfertype= MOVE > logfile = AUTO > progressbar = YES > > This RRR|ArxToHTML call will create HTML pages based on an ARX-file > and a DEF-file with the form definition: > rrrArxToHTML.pl -suppressnull -d "c:\archivehtml\schema.def" -a > "c:\archive\HPD_Help_Desk_Archive.arx" -t "c:\archivehtml\html" > > ADV: If you want a supported solution, you can always sign up for > support on RRR|Chive, which is otherwise free to use. Just ask for a quote. > > Best Regards - Misi, RRR AB, http://rrr.se > >> Robin, >> Both of these could be handled by RRR|Chive. >> www.rrr.se >> >> Misi's tools are very straight forward. >> >> Thank you, >> --- >> John J. Reiser >> Remedy Developer/Administrator >> Senior Software Development Analyst >> Lockheed Martin - MS2 >> The star that burns twice as bright burns half as long. >> Pay close attention and be illuminated by its brilliance. - >> paraphrased by me >> >> >> -Or
Re: EXTERNAL: Help on archiving data.
Thanks for the reply. I have two options infront of me. 1) Use DB Script 2) Use RRRchive Can you please let me know the advantages of RRRchive over DB script for archiving? Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
RRR|Chive will use ARS API. That means that the workflow will be fired and it can be slow (because of your ARS server, not because RRR|Chive. Also both source and destiny must be ARS servers (can be the same). DB is faster but you are doing things outside ARS. That means that it's not supported, that you can corrupt the ARS database if not done well and some other risks. If speed of archiving is a concern... then DB is the only option to go faster. Jose Manuel Huerta http://theremedyforit.com/ On Wed, Aug 8, 2012 at 1:35 PM, Robin Mathew wrote: > RRRchiv ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Hi, There is an option to disable workflow on the target form: target_disablemergefltr = YES There is also an option for the delete in the source form: source_disabledeletefltr = YES The problem with the delete-filter is that RRR|Chive needs to disable the filter completely, and that is an admin change. Instead you can add this to any Delete-filter on the forms you are archiving: Execute on: Delete Run if: (...) AND $CLIENT-TYPE$ != Finally, RRR|Chive can archive things to ARX flat files, which do not require a Remedy target. You can then, as I mentioned earlier, use RRR|ArxToHTML to create HTML web pages of the ARX-files, which can be accessed with any browser. Either on a web server or on a file system: http://rrr.se/itsmdoc/itsm764arxhtml/ And yes, it can be a little bit slower to use the API, but the pros definitely outweighs the cons I think. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > RRR|Chive will use ARS API. That means that the workflow will be fired and > it can be slow (because of your ARS server, not because RRR|Chive. Also > both source and destiny must be ARS servers (can be the same). > > DB is faster but you are doing things outside ARS. That means that it's > not > supported, that you can corrupt the ARS database if not done well and some > other risks. > > If speed of archiving is a concern... then DB is the only option to go > faster. > > Jose Manuel Huerta > http://theremedyforit.com/ > > > > > On Wed, Aug 8, 2012 at 1:35 PM, Robin Mathew > wrote: > >> RRRchiv > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Agree Jose Manuel Huerta http://theremedyforit.com/ On Wed, Aug 8, 2012 at 1:41 PM, Misi Mladoniczky wrote: > > > You can then, as I mentioned earlier, use RRR|ArxToHTML to create HTML web > pages of the ARX-files, which can be accessed with any browser. Either on > a web server or on a file system: http://rrr.se/itsmdoc/itsm764arxhtml/ > > And yes, it can be a little bit slower to use the API, but the pros > definitely outweighs the cons I think. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Thanks Misi and Jose for your reply. Misi, Changing the Filter qualification on the source form is a good idea. If I propose RRRchive as a solution for archiving,the first concern comes in everyone's mind will be the performance impact on the application server as it uses API. Can you please let me know your more suggestions for overcoming application slowness? Regards Robin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Help on archiving data.
Hi,
If you run the archiving scripts often, the impact will be less.
In any event, the impact should be light, as RRR|Chive normally does not
trigger any table scans.
If a lot of records are archived ("deleted") at the same time, this might
have a small impact.
Records are merged and deleted one at a time, which minimize the impact.
The records are retrieved in chunks of 100, which is not much.
You can even set a parameter to slow things down even further, and in this
example would do a 2 second pause between each record:
nicepausetime=2
You can even decrease the 100-chunk to a lower value. For example 1 at a
time:
multientrychunksize=1
I usually do not use these settings, as impact is minimally affected
anyway. In any event the nicepausetime=1 would limit the number of
archived records to 3600 per hour...
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Thanks Misi and Jose for your reply.
>
> Misi,
>
> Changing the Filter qualification on the source form is a good idea.
>
> If I propose RRRchive as a solution for archiving,the first concern comes
> in everyone's mind will be the performance impact on the application
> server as it uses API.
>
> Can you please let me know your more suggestions for overcoming
> application slowness?
>
> Regards
> Robin
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
