Re: BMC Remedy - Copy to Archive and Delete from Source

[Thivagar Sankaran]

Hi Mel,

 

Recently I have archived the data in my 6.3 environment. I have done this to
improve the performance and I observe the performance has been improved
considerably. But the issue was, the Copy to Archive and Delete from Source
option was not working in my environment. Hence I went for Copy to Archive
Option and deleted the data manually. I have raised this issue with BMC. But
as usual I didn't get a proper response.

 

Thanks & Regards,

Thivagar Sankaran

ITIL - Foundataion Certified

Remedy Developer

 

  _  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Melanie Snayer
Sent: Wednesday, March 26, 2008 2:44 PM
To: arslist@ARSLIST.ORG
Subject: BMC Remedy - Copy to Archive and Delete from Source

 

** 

Hi Listeners

 

We're experiencing performance issues especially when submitting incidents.
Our initial plan was to archive calls that have been closed for more than 5
years but as a result of the performance issues we're having to considering
archiving as soon as 1 year and 6 months after having gone-live. Well,
archiving is just one of the options that we have resorted to along side the
current ongoing perfomance tuning that we're doing.

 

Can you guys give me examples of how you may have gone about archiving your
data? Like what the archiving criteria is and whether your archiving was
done as a result of performance issue or as standard procedure.

 

Thanks

Mel

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"


smime.p7s
Description: S/MIME cryptographic signature

Re: BMC Remedy - Copy to Archive and Delete from Source

[Melanie Snayer]

Hey Thivagar

We are in a 7.01 environment but I'm glad to know that this improved on
performance. Could you perhaps give me a rough indication of the
following information:

   - what your database size is
   - number of records before the archive
   - time taken to save a call before the archive
   - number of records after the archive
   - time taken to save a call after the archive

Anyone else like to share a bit of their archiving info with me?

Regards
Mel

On 3/26/08, Thivagar Sankaran <[EMAIL PROTECTED]> wrote:

> **
>
> Hi Mel,
>
>
>
> Recently I have archived the data in my 6.3 environment. I have done this
> to improve the performance and I observe the performance has been improved
> considerably. But the issue was, the Copy to Archive and Delete from
> Source option was not working in my environment. Hence I went for Copy to
> Archive Option and deleted the data manually. I have raised this issue with
> BMC. But as usual I didn't get a proper response.
>
>
>
> Thanks & Regards,
>
> Thivagar Sankaran
>
> ITIL – Foundataion Certified
>
> Remedy Developer
>
>
>  --
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Melanie Snayer
> *Sent:* Wednesday, March 26, 2008 2:44 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* BMC Remedy - Copy to Archive and Delete from Source
>
>
>
> **
>
> Hi Listeners
>
>
>
> We're experiencing performance issues especially when submitting
> incidents. Our initial plan was to archive calls that have been closed for
> more than 5 years but as a result of the performance issues we're having to
> considering archiving as soon as 1 year and 6 months after having gone-live.
> Well, archiving is just one of the options that we have resorted to along
> side the current ongoing perfomance tuning that we're doing.
>
>
>
> Can you guys give me examples of how you may have gone about archiving
> your data? Like what the archiving criteria is and whether your archiving
> was done as a result of performance issue or as standard procedure.
>
>
>
> Thanks
>
> Mel
>
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: BMC Remedy - Copy to Archive and Delete from Source

[Brittain, Mark]

Hi All
 
I am having a similar problem with the Copy to Archive and Delete from Source. 
I set up the archive form and at first the archiving worked fine. Then I made 
some changes to the main form and the archiving stopped and the archive tab 
information is no blank. I tried to start up the archiving again and got the 
error that the archive form was not valid. I understood that changes to the 
main form would carryover the the archive. Well they did not.
 
ARS 6.3 patch 20
SunOS 5.9
Oracle 9.2.0.7
 
Anybody have any ideas?
 
Thanks
Mark



From: Action Request System discussion list(ARSList) on behalf of Thivagar 
Sankaran
Sent: Wed 3/26/2008 5:25 AM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source


** 

Hi Mel,

 

Recently I have archived the data in my 6.3 environment. I have done this to 
improve the performance and I observe the performance has been improved 
considerably. But the issue was, the Copy to Archive and Delete from Source 
option was not working in my environment. Hence I went for Copy to Archive 
Option and deleted the data manually. I have raised this issue with BMC. But as 
usual I didn't get a proper response.

 

Thanks & Regards,

Thivagar Sankaran

ITIL - Foundataion Certified

Remedy Developer

 



From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Melanie Snayer
Sent: Wednesday, March 26, 2008 2:44 PM
To: arslist@ARSLIST.ORG
Subject: BMC Remedy - Copy to Archive and Delete from Source

 

** 

Hi Listeners

 

We're experiencing performance issues especially when submitting incidents. Our 
initial plan was to archive calls that have been closed for more than 5 years 
but as a result of the performance issues we're having to considering archiving 
as soon as 1 year and 6 months after having gone-live. Well, archiving is just 
one of the options that we have resorted to along side the current ongoing 
perfomance tuning that we're doing.

 

Can you guys give me examples of how you may have gone about archiving your 
data? Like what the archiving criteria is and whether your archiving was done 
as a result of performance issue or as standard procedure.

 

Thanks

Mel

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ 

This e-mail is the property of NaviSite, Inc. It is intended only
for the person or entity to which it is addressed and may contain
information that is privileged, confidential, or otherwise protected
from disclosure. Distribution or copying of this e-mail, or the
information contained herein, to anyone other than the intended
recipient is prohibited.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: BMC Remedy - Copy to Archive and Delete from Source

[Joseph Kasell]

Mel,

We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
month ago, it was sorely needed, and it certainly has made a difference.
Since Remedy was put into production back in the summer of 2004, approx
390,000 tickets had been submitted.  The amount of tickets had not been a
problem until recently when we began to see performance lags performing
various actions in Remedy.  Opening an existing Help Desk ticket from the
Remedy Support console alone was taking anywhere from 1 to 5 seconds
depending on the ticket (API and SQL logs were very helpful here).

We decided to archive all Help Desk tickets with a status of Closed that
were older than 13 months.  We considered using Remedy's archiving feature,
but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
lab testing indicated that the archiving of an estimated 250,000 tickets
would take about 6 to 7 hours (and slow the system down tremendously), we
decided to archive in chunks of 40,000 which limited the performance pain
to about an hour.  We did this for 7 nights in a row.  I can tell you that
since, performance has improved tremendously (max time to open an existing
ticket is about a second).  Archiving is done nightly now.  It takes a
minute to archive the 400 to 500 tickets that meet the archive criteria.  I
know that my users are happy.

Joe

Joseph Kasell
Navy Federal Credit Union



   
 Melanie Snayer
 <[EMAIL PROTECTED] 
 MAIL.COM>  To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
 ORG>  and Delete from Source  
   
   
 03/26/2008 05:45  
 AM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




--=_Part_6872_1105761.1206524742321
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hey Thivagar

We are in a 7.01 environment but I'm glad to know that this improved on
performance. Could you perhaps give me a rough indication of the
following information:

   - what your database size is
   - number of records before the archive
   - time taken to save a call before the archive
   - number of records after the archive
   - time taken to save a call after the archive

Anyone else like to share a bit of their archiving info with me?

Regards
Mel

On 3/26/08, Thivagar Sankaran <[EMAIL PROTECTED]> wrote:

> **
>
> Hi Mel,
>
>
>
> Recently I have archived the data in my 6.3 environment. I have done this
> to improve the performance and I observe the performance has been
improve=
d
> considerably. But the issue was, the Copy to Archive and Delete from
> Source option was not working in my environment. Hence I went for Copy to
> Archive Option and deleted the data manually. I have raised this issue
wi=
th
> BMC. But as usual I didn't get a proper response.
>
>
>
> Thanks & Regards,
>
> Thivagar Sankaran
>
> ITIL =96 Foundataion Certified
>
> Remedy Developer
>
>
>  --
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Melanie Snayer
> *Sent:* Wednesday, March 26, 2008 2:44 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* BMC Remedy - Copy to Archive and Delete from Source
>
>
>
> **
>
> Hi Listeners
>
>
>
> We're experiencing performance issues especially when submitting
> incidents. Our initial plan was to archive calls that have been closed
fo=
r
> more than 5 years but as a result of the performance issues we're having
=
to
> considering archiving as soon as 1 year and 6 months after having
gone-li=
ve.
> Well, archiving is just one of the options that we have resorted to along
> side the current ongoing perfomance 

Re: BMC Remedy - Copy to Archive and Delete from Source

[Melanie Snayer]

Hi Joe

Thanks so much for this information. Would you perhaps be able to tell me
whether there was a delay on saving Help Desk tickets before you archived?

Regards
Mel


On 3/26/08, Joseph Kasell <[EMAIL PROTECTED]> wrote:
>
> Mel,
>
> We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
> month ago, it was sorely needed, and it certainly has made a difference.
> Since Remedy was put into production back in the summer of 2004, approx
> 390,000 tickets had been submitted.  The amount of tickets had not been a
> problem until recently when we began to see performance lags performing
> various actions in Remedy.  Opening an existing Help Desk ticket from the
> Remedy Support console alone was taking anywhere from 1 to 5 seconds
> depending on the ticket (API and SQL logs were very helpful here).
>
> We decided to archive all Help Desk tickets with a status of Closed that
> were older than 13 months.  We considered using Remedy's archiving
> feature,
> but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
> lab testing indicated that the archiving of an estimated 250,000 tickets
> would take about 6 to 7 hours (and slow the system down tremendously), we
> decided to archive in chunks of 40,000 which limited the performance pain
> to about an hour.  We did this for 7 nights in a row.  I can tell you that
> since, performance has improved tremendously (max time to open an existing
> ticket is about a second).  Archiving is done nightly now.  It takes a
> minute to archive the 400 to 500 tickets that meet the archive
> criteria.  I
> know that my users are happy.
>
> Joe
>
> Joseph Kasell
> Navy Federal Credit Union
>
>
>
>
> Melanie Snayer
> <[EMAIL PROTECTED]
> MAIL.COM>  To
> Sent by: "Action  arslist@ARSLIST.ORG
> Request System cc
> discussion
> list(ARSList)"Subject
> <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
> ORG>  and Delete from Source
>
>
> 03/26/2008 05:45
> AM
>
>
> Please respond to
> [EMAIL PROTECTED]
>RG
>
>
>
>
>
>
> --=_Part_6872_1105761.1206524742321
> Content-Type: text/plain; charset=WINDOWS-1252
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> Hey Thivagar
>
> We are in a 7.01 environment but I'm glad to know that this improved on
> performance. Could you perhaps give me a rough indication of the
> following information:
>
>   - what your database size is
>   - number of records before the archive
>   - time taken to save a call before the archive
>   - number of records after the archive
>   - time taken to save a call after the archive
>
> Anyone else like to share a bit of their archiving info with me?
>
> Regards
> Mel
>
> On 3/26/08, Thivagar Sankaran <[EMAIL PROTECTED]> wrote:
>
> > **
> >
> > Hi Mel,
> >
> >
> >
> > Recently I have archived the data in my 6.3 environment. I have done
> this
> > to improve the performance and I observe the performance has been
> improve=
> d
> > considerably. But the issue was, the Copy to Archive and Delete from
> > Source option was not working in my environment. Hence I went for Copy
> to
> > Archive Option and deleted the data manually. I have raised this issue
> wi=
> th
> > BMC. But as usual I didn't get a proper response.
> >
> >
> >
> > Thanks & Regards,
> >
> > Thivagar Sankaran
> >
> > ITIL =96 Foundataion Certified
> >
> > Remedy Developer
> >
> >
> >  --
> >
> > *From:* Action Request System discussion list(ARSList) [mailto:
> > [EMAIL PROTECTED] *On Behalf Of *Melanie Snayer
> > *Sent:* Wednesday, March 26, 2008 2:44 PM
> > *To:* arslist@ARSLIST.ORG
> > *Subject:* BMC Remedy - Copy to Archive and Delete from Source
> >
> >
> >
> > **
> >
> > Hi Listeners
> >
> >
> >
> > We're experiencing performance issues especially when submitting
> > incidents. Our initial plan was to archive calls that have been closed
> fo=
> r
> > more than 5 years but as a result of the performance issues we're having
> =
> to
> > considering archiving as soon as 1 year and 6 months after having
> gone-li=
> ve.
> > Well, archiving is just one of the options that we have resorted to
> along
> > side the current ongoing perfomance tuning that we're doing.
> >
> >
> >
> > Can you guys give me examples of how you may have gone about archiving
> > your data? Like what the archiving criteria is and whether your
> archiving
> > was done as a result of performance issue or as standard procedure.
> >
> >
> >
> > Thanks
> >
> > Mel
> >
> > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> > html___
> > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> > html___
> >
>
>
> ___

Re: BMC Remedy - Copy to Archive and Delete from Source

[Joseph Kasell]

Mel,

We didn't measure that specifically before and after archiving, but our
users are telling us that the response for that activity is better.

Joe

Joseph Kasell
Navy Federal Credit Union



   
 Melanie Snayer
 <[EMAIL PROTECTED] 
 MAIL.COM>  To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
 ORG>  and Delete from Source  
   
   
 03/26/2008 09:28  
 AM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




--=_Part_7293_11795538.1206538125823
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Joe

Thanks so much for this information. Would you perhaps be able to tell me
whether there was a delay on saving Help Desk tickets before you archived?

Regards
Mel


On 3/26/08, Joseph Kasell <[EMAIL PROTECTED]> wrote:
>
> Mel,
>
> We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
> month ago, it was sorely needed, and it certainly has made a difference.
> Since Remedy was put into production back in the summer of 2004, approx
> 390,000 tickets had been submitted.  The amount of tickets had not been a
> problem until recently when we began to see performance lags performing
> various actions in Remedy.  Opening an existing Help Desk ticket from the
> Remedy Support console alone was taking anywhere from 1 to 5 seconds
> depending on the ticket (API and SQL logs were very helpful here).
>
> We decided to archive all Help Desk tickets with a status of Closed that
> were older than 13 months.  We considered using Remedy's archiving
> feature,
> but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
> lab testing indicated that the archiving of an estimated 250,000 tickets
> would take about 6 to 7 hours (and slow the system down tremendously), we
> decided to archive in chunks of 40,000 which limited the performance pain
> to about an hour.  We did this for 7 nights in a row.  I can tell you
that
> since, performance has improved tremendously (max time to open an
existing
> ticket is about a second).  Archiving is done nightly now.  It takes a
> minute to archive the 400 to 500 tickets that meet the archive
> criteria.  I
> know that my users are happy.
>
> Joe
>
> Joseph Kasell
> Navy Federal Credit Union
>
>
>
>
> Melanie Snayer
> <[EMAIL PROTECTED]
> MAIL.COM>  To
> Sent by: "Action  arslist@ARSLIST.ORG
> Request System cc
> discussion
> list(ARSList)"Subject
> <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
> ORG>  and Delete from Source
>
>
> 03/26/2008 05:45
> AM
>
>
> Please respond to
> [EMAIL PROTECTED]
>RG
>
>
>
>
>
>
> --=_Part_6872_1105761.1206524742321
> Content-Type: text/plain; charset=WINDOWS-1252
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> Hey Thivagar
>
> We are in a 7.01 environment but I'm glad to know that this improved on
> performance. Could you perhaps give me a rough indication of the
> following information:
>
>   - what your database size is
>   - number of records before the archive
>   - time taken to save a call before the archive
>   - number of records after the archive
>   - time taken to save a call after the archive
>
> Anyone else like to share a bit of their archiving info with me?
>
> Regards
> Mel
>
> On 3/26/08, Thivagar Sankaran <[EMAI

Re: BMC Remedy - Copy to Archive and Delete from Source

[Susan Palmer]

Mel,

I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
those forms keeps performance at an acceptable level.  You have to remember
that all workflow is affected by the number of records in the form and keep
in mind any table fields that are refreshed.

We generally keep 13 months of or closed records.

Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
option.  In the last month I've used it on HTs, Tasks and email messages.
For us it appears to require a huge amount of disk space for the copy/delete
option.  That needs to be planned for and it was greater than 1 for 1 which
is logical since another table is now holding the same record.  For us it
was quite a bit more than that infact we nearly brought the server down.

I only archive in the lowest of production hours (night) when minimal users
are on the system.

I was also notified yesterday that it is not recommended to archive system
email messages, there is some unusal result related to it.  Sorry did not
get more info.

I found the actual archiving to go fairly quick, was doing about 70k records
both times.  I liked the fact I didn't have to manually delete the records
afterwards.

hth,
Susan

ShopperTrak

On Wed, Mar 26, 2008 at 8:28 AM, Melanie Snayer <[EMAIL PROTECTED]>
wrote:

> ** Hi Joe
>
> Thanks so much for this information. Would you perhaps be able to tell me
> whether there was a delay on saving Help Desk tickets before you archived?
>
> Regards
> Mel
>
>
>   On 3/26/08, Joseph Kasell <[EMAIL PROTECTED]> wrote:
> >
> > Mel,
> >
> > We're running 7.0.1 with ITSM 6.  We instituted archiving a little over
> > a
> > month ago, it was sorely needed, and it certainly has made a difference.
> > Since Remedy was put into production back in the summer of 2004, approx
> > 390,000 tickets had been submitted.  The amount of tickets had not been
> > a
> > problem until recently when we began to see performance lags performing
> > various actions in Remedy.  Opening an existing Help Desk ticket from
> > the
> > Remedy Support console alone was taking anywhere from 1 to 5 seconds
> > depending on the ticket (API and SQL logs were very helpful here).
> >
> > We decided to archive all Help Desk tickets with a status of Closed that
> > were older than 13 months.  We considered using Remedy's archiving
> > feature,
> > but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
> > lab testing indicated that the archiving of an estimated 250,000 tickets
> > would take about 6 to 7 hours (and slow the system down tremendously),
> > we
> > decided to archive in chunks of 40,000 which limited the performance
> > pain
> > to about an hour.  We did this for 7 nights in a row.  I can tell you
> > that
> > since, performance has improved tremendously (max time to open an
> > existing
> > ticket is about a second).  Archiving is done nightly now.  It takes a
> > minute to archive the 400 to 500 tickets that meet the archive
> > criteria.  I
> > know that my users are happy.
> >
> > Joe
> >
> > Joseph Kasell
> > Navy Federal Credit Union
> >
> >
> >
> >
> > Melanie Snayer
> > <[EMAIL PROTECTED]
> > MAIL.COM 
> > >  To
> > Sent by: "Action  arslist@ARSLIST.ORG
> > Request System
> > cc
> > discussion
> >
> > list(ARSList)"Subject
> > <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
> > ORG>  and Delete from Source
> >
> >
> > 03/26/2008 05:45
> > AM
> >
> >
> > Please respond to
> > [EMAIL PROTECTED]
> >RG
> >
> >
> >
> >
> >
> >
> > --=_Part_6872_1105761.1206524742321
> > Content-Type: text/plain; charset=WINDOWS-1252
> > Content-Transfer-Encoding: quoted-printable
> > Content-Disposition: inline
> >
> > Hey Thivagar
> >
> > We are in a 7.01 environment but I'm glad to know that this improved on
> > performance. Could you perhaps give me a rough indication of the
> > following information:
> >
> >   - what your database size is
> >   - number of records before the archive
> >   - time taken to save a call before the archive
> >   - number of records after the archive
> >   - time taken to save a call after the archive
> >
> > Anyone else like to share a bit of their archiving info with me?
> >
> > Regards
> > Mel
> >
> > On 3/26/08, Thivagar Sankaran <[EMAIL PROTECTED]> wrote:
> >
> > > **
> > >
> > > Hi Mel,
> > >
> > >
> > >
> > > Recently I have archived the data in my 6.3 environment. I have done
> > this
> > > to improve the performance and I observe the performance has been
> > improve=
> > d
> > > considerably. But the issue was, the Copy to Archive and Delete from
> > > Source option was not working in my environment. Hence I went for Copy
> > to
> > > Archive Option and deleted 

Re: BMC Remedy - Copy to Archive and Delete from Source

[Chintan Shah]

Mel,

Last weekend we archived 120,000 records in less than 3 hours.

We have 2 servers(production and reporting). Data gets DSO'ed from production 
to reporting all the time. So, we actually performed archiving on reporting 
server.

We only used "Copy to Archive" functionality. There was no performance impact 
whatsoever during the entire proecess.  I have not tested "copy to archive and 
delete from source" functionality.

Our approach was like this
1. Take backup of all records you want to delete( in .arx file).
2. Have DBA take backup in a .dmp file.
3. Start "Copy to Archive" on the form you want to archive.

Verify that we have same number of records(based on criteria u specify) on 
archived form as we have on source form.

Now, the BIG part. We experience memory issues while deleting data using 
escalation.  One of our consultants proposed an excellent solution for deleting 
data. 

1. Export only ID's of the records that you want to delete in .arx file. Use 
same criteria as you used for archiving.
2. Use a filter that fires on "Merge" and that performs an 
Application-Delete-Entry operation.

This approach is as good as deleting 1 record at a time and has NO impact on 
server whatsoever.

So, as soon as you start importing the data through "Remedy Import Tool", 
filter will fire and it will delete the record from production. As we have DSO 
in place, it will eventually delete from other server too.

If you don't have separate reporting server, then you are pretty much done with 
process. 

It took almost 12:30 hours to delete all records with no user impact.
 
By the way, I have a question. Is there any documentation available saying that 
"This is the max limit that Remedy can handle for good performance". 

Some of our forms have more than million records. Thanks for help in advance.

Hope this helps.

Thanks
Chintan.

Joseph Kasell <[EMAIL PROTECTED]> wrote: Mel,

We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
month ago, it was sorely needed, and it certainly has made a difference.
Since Remedy was put into production back in the summer of 2004, approx
390,000 tickets had been submitted.  The amount of tickets had not been a
problem until recently when we began to see performance lags performing
various actions in Remedy.  Opening an existing Help Desk ticket from the
Remedy Support console alone was taking anywhere from 1 to 5 seconds
depending on the ticket (API and SQL logs were very helpful here).

We decided to archive all Help Desk tickets with a status of Closed that
were older than 13 months.  We considered using Remedy's archiving feature,
but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
lab testing indicated that the archiving of an estimated 250,000 tickets
would take about 6 to 7 hours (and slow the system down tremendously), we
decided to archive in chunks of 40,000 which limited the performance pain
to about an hour.  We did this for 7 nights in a row.  I can tell you that
since, performance has improved tremendously (max time to open an existing
ticket is about a second).  Archiving is done nightly now.  It takes a
minute to archive the 400 to 500 tickets that meet the archive criteria.  I
know that my users are happy.

Joe

Joseph Kasell
Navy Federal Credit Union



   
 Melanie Snayer
 
 MAIL.COM>  To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 
 ORG>  and Delete from Source  
   
   
 03/26/2008 05:45  
 AM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




--=_Part_6872_1105761.1206524742321
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hey Thivagar

We are in a 7.01 environment but I'm glad to

Re: BMC Remedy - Copy to Archive and Delete from Source

[Thad K Esser]

Joe,

Properly indexed and tuned 400,000 tickets on a form shouldn't be a 
problem.  To expand on what Susan indicated, nine times out of ten, the 
biggest cause of slowness when opening forms is table fields that are 
needlessly being refreshed.  Watch out for tables being refreshed on 
hidden tabs.  Have an active link that fires on Gain Focus (of that tab) 
AND also on Display, with a run if of ('Page Holder' = "Tab Name').  The 
one action would be the table refresh.

Of course there are other causes for slowness on opening of forms, but 
I've found this is the most common, and typically the easiest to fix. (oh, 
and be suspect of any active link that fires on all three of Window Open, 
Window Loaded, and Display - its probably running three times when you 
display a ticket).

Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard 
Bach



"Susan Palmer" <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)" 

03/26/2008 08:27 AM
Please respond to
arslist@ARSLIST.ORG


To
arslist@ARSLIST.ORG
cc

Subject
Re: BMC Remedy - Copy to Archive and Delete from Source






** 
Mel,
 
I have found that for 'us' keeping less than 100k Help Tickets or Tasks in 
those forms keeps performance at an acceptable level.  You have to 
remember that all workflow is affected by the number of records in the 
form and keep in mind any table fields that are refreshed.
 
We generally keep 13 months of or closed records. 
 
Since we upgraded to v7.0.1P3 last year I was excited about the 'archive' 
option.  In the last month I've used it on HTs, Tasks and email messages. 
For us it appears to require a huge amount of disk space for the 
copy/delete option.  That needs to be planned for and it was greater than 
1 for 1 which is logical since another table is now holding the same 
record.  For us it was quite a bit more than that infact we nearly brought 
the server down.
 
I only archive in the lowest of production hours (night) when minimal 
users are on the system.
 
I was also notified yesterday that it is not recommended to archive system 
email messages, there is some unusal result related to it.  Sorry did not 
get more info.
 
I found the actual archiving to go fairly quick, was doing about 70k 
records both times.  I liked the fact I didn't have to manually delete the 
records afterwards. 
 
hth,
Susan
 
ShopperTrak

On Wed, Mar 26, 2008 at 8:28 AM, Melanie Snayer <[EMAIL PROTECTED]> 
wrote:
** 
Hi Joe
 
Thanks so much for this information. Would you perhaps be able to tell me 
whether there was a delay on saving Help Desk tickets before you archived?
 
Regards
Mel

 
On 3/26/08, Joseph Kasell <[EMAIL PROTECTED]> wrote: 
Mel,

We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
month ago, it was sorely needed, and it certainly has made a difference.
Since Remedy was put into production back in the summer of 2004, approx
390,000 tickets had been submitted.  The amount of tickets had not been a
problem until recently when we began to see performance lags performing
various actions in Remedy.  Opening an existing Help Desk ticket from the
Remedy Support console alone was taking anywhere from 1 to 5 seconds
depending on the ticket (API and SQL logs were very helpful here).

We decided to archive all Help Desk tickets with a status of Closed that
were older than 13 months.  We considered using Remedy's archiving 
feature,
but eventually went with Misi Mladoniczky's rrrchive utility.  Since our
lab testing indicated that the archiving of an estimated 250,000 tickets
would take about 6 to 7 hours (and slow the system down tremendously), we
decided to archive in chunks of 40,000 which limited the performance pain
to about an hour.  We did this for 7 nights in a row.  I can tell you that
since, performance has improved tremendously (max time to open an existing
ticket is about a second).  Archiving is done nightly now.  It takes a
minute to archive the 400 to 500 tickets that meet the archive criteria. I
know that my users are happy.

Joe

Joseph Kasell
Navy Federal Credit Union




Melanie Snayer
<[EMAIL PROTECTED]
MAIL.COM>  To
Sent by: "Action  arslist@ARSLIST.ORG
Request System cc
discussion
list(ARSList)"Subject
<[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
ORG>  and Delete from Source


03/26/2008 05:45
AM


Please respond to
[EMAIL PROTECTED]
   RG






--=_Part_6872_1105761.1206524742321
Content-Type: text/plain; charset=WINDOWS-1252
Conte

Re: BMC Remedy - Copy to Archive and Delete from Source

[James Van Sickle]

In response to Susan's comments about archiving the AR System Email
Messages form:

According to Remedy Support, creating an Archive Form for the AR System
Email Messages form causes a duplication of the reserved fields used by the
email engine to send email.  Apparently the email engine was not setup to
distinguish Field IDs such as 18085 between two separate forms.  When I
created an Archive form off the Email Messages form, the Email Engine
decided that my Archived Email Messages form was the new form to process
incoming and outgoing email on.  This became somewhat amusing as Incoming
email went directly to my Archive Form, and Outgoing email just sat in my
original Email Messages form waiting to get processed.

Removing the Archive form and restarting the Email Engine fixes the
problem.

(Embedded image moved to file: pic14989.gif)Countrywide


James Van Sickle
Remedy Developer II
IT - Enterprise Change & Config


 
 972-696-5779 Office  1000 Coit Road 
   92-540-5779Mail Stop: PCRD-2-78   
 Internal Plano, TX 75075
 






   
 Thad K Esser  
 <[EMAIL PROTECTED] 
 COM>   To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 <[EMAIL PROTECTED] Re: [ARSLIST] BMC Remedy - Copy to  
 ORG>  Archive and Delete from Source  
   
   
 03/26/2008 01:43  
 PM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




**
Joe,

Properly indexed and tuned 400,000 tickets on a form shouldn't be a
problem.  To expand on what Susan indicated, nine times out of ten, the
biggest cause of slowness when opening forms is table fields that are
needlessly being refreshed.  Watch out for tables being refreshed on hidden
tabs.  Have an active link that fires on Gain Focus (of that tab) AND also
on Display, with a run if of ('Page Holder' = "Tab Name').  The one action
would be the table refresh.

Of course there are other causes for slowness on opening of forms, but I've
found this is the most common, and typically the easiest to fix.  (oh, and
be suspect of any active link that fires on all three of Window Open,
Window Loaded, and Display - its probably running three times when you
display a ticket).

Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard
Bach

   
 "Susan Palmer" <[EMAIL PROTECTED]>
 Sent by: "Action Request System   
 discussion list(ARSList)"  To 
arslist@ARSLIST.ORG   
cc 
   
 03/26/2008 08:27 AM   Subject 
 Re: BMC Remedy - Copy 
 to Archive and Delete 
 Please respond to   from Source   
arslist@ARSLIST.ORG
   
   
   
   
   
  

Re: BMC Remedy - Copy to Archive and Delete from Source

[Joseph Kasell]

Thad,

You bring up an excellent point regarding tables.  Case in point in the
Requester's Cases table under the Requester Information tab on the Help
Desk form.  Along with tickets reported by end-users we also have tickets
generated from Patrol, and all those tickets have the same Requester.
Needless to say there are a lot more of those tickets than those called-in
by our regular (i.e. - "human") users.  So when a ticket for that
particular Requester is opened from the Support Console, there is quite the
lag due to the query used to populate the Requester's Cases table.  The
client SQL and API logs were a real eye-opener insofar as that was
concerned.

Joe

Joseph Kasell
Navy Federal Credit Union




   
 Thad K Esser  
 <[EMAIL PROTECTED] 
 COM>   To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
 ORG>  and Delete from Source  
   
   
 03/26/2008 02:42  
 PM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




This is a multipart message in MIME format.
--=_alternative 0066B95B88257418_=
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit

Joe,

Properly indexed and tuned 400,000 tickets on a form shouldn't be a
problem.  To expand on what Susan indicated, nine times out of ten, the
biggest cause of slowness when opening forms is table fields that are
needlessly being refreshed.  Watch out for tables being refreshed on
hidden tabs.  Have an active link that fires on Gain Focus (of that tab)
AND also on Display, with a run if of ('Page Holder' = "Tab Name').  The
one action would be the table refresh.

Of course there are other causes for slowness on opening of forms, but
I've found this is the most common, and typically the easiest to fix. (oh,
and be suspect of any active link that fires on all three of Window Open,
Window Loaded, and Display - its probably running three times when you
display a ticket).

Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard
Bach



"Susan Palmer" <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)"

03/26/2008 08:27 AM
Please respond to
arslist@ARSLIST.ORG


To
arslist@ARSLIST.ORG
cc

Subject
Re: BMC Remedy - Copy to Archive and Delete from Source






**
Mel,

I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
those forms keeps performance at an acceptable level.  You have to
remember that all workflow is affected by the number of records in the
form and keep in mind any table fields that are refreshed.

We generally keep 13 months of or closed records.

Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
option.  In the last month I've used it on HTs, Tasks and email messages.
For us it appears to require a huge amount of disk space for the
copy/delete option.  That needs to be planned for and it was greater than
1 for 1 which is logical since another table is now holding the same
record.  For us it was quite a bit more than that infact we nearly brought
the server down.

I only archive in the lowest of production hours (night) when minimal
users are on the system.

I was also notified yesterday that it is not recommended to archive system
email messages, there is some unusal result related to it.  Sorry did not
get more info.

I found the actual archiving to go fairly quick, was doing about 70k
records both times.  I liked the fact I didn't have to manually delete the
records afterwards.

hth,
Susan

ShopperTrak

On Wed, 

Re: BMC Remedy - Copy to Archive and Delete from Source

[Susan Palmer]

Thanks for the info James, alot more detail than I had.  I've deleted that
archive form!

Thanks,
Susan

On Wed, Mar 26, 2008 at 2:07 PM, James Van Sickle <
[EMAIL PROTECTED]> wrote:

> In response to Susan's comments about archiving the AR System Email
> Messages form:
>
> According to Remedy Support, creating an Archive Form for the AR System
> Email Messages form causes a duplication of the reserved fields used by
> the
> email engine to send email.  Apparently the email engine was not setup to
> distinguish Field IDs such as 18085 between two separate forms.  When I
> created an Archive form off the Email Messages form, the Email Engine
> decided that my Archived Email Messages form was the new form to process
> incoming and outgoing email on.  This became somewhat amusing as Incoming
> email went directly to my Archive Form, and Outgoing email just sat in my
> original Email Messages form waiting to get processed.
>
> Removing the Archive form and restarting the Email Engine fixes the
> problem.
>
> (Embedded image moved to file: pic14989.gif)Countrywide
>
>
> James Van Sickle
> Remedy Developer II
> IT - Enterprise Change & Config
>
>
>
>  972-696-5779 Office  1000 Coit Road
>   92-540-5779Mail Stop: PCRD-2-78
>  Internal Plano, TX 75075
>
>
>
>
>
>
>
>
> Thad K Esser
> <[EMAIL PROTECTED]
> COM>   To
> Sent by: "Action  arslist@ARSLIST.ORG
> Request System cc
> discussion
> list(ARSList)"Subject
> <[EMAIL PROTECTED] Re: [ARSLIST] BMC Remedy - Copy to
> ORG>  Archive and Delete from Source
>
>
> 03/26/2008 01:43
> PM
>
>
> Please respond to
> [EMAIL PROTECTED]
>RG
>
>
>
>
>
>
> **
> Joe,
>
> Properly indexed and tuned 400,000 tickets on a form shouldn't be a
> problem.  To expand on what Susan indicated, nine times out of ten, the
> biggest cause of slowness when opening forms is table fields that are
> needlessly being refreshed.  Watch out for tables being refreshed on
> hidden
> tabs.  Have an active link that fires on Gain Focus (of that tab) AND also
> on Display, with a run if of ('Page Holder' = "Tab Name').  The one action
> would be the table refresh.
>
> Of course there are other causes for slowness on opening of forms, but
> I've
> found this is the most common, and typically the easiest to fix.  (oh, and
> be suspect of any active link that fires on all three of Window Open,
> Window Loaded, and Display - its probably running three times when you
> display a ticket).
>
> Thad Esser
> Remedy Developer
> "Argue for your limitations, and sure enough, they're yours."-- Richard
> Bach
>
>
>  "Susan Palmer" <[EMAIL PROTECTED]>
>  Sent by: "Action Request System
>  discussion list(ARSList)"  To
> arslist@ARSLIST.ORG
>cc
>
>  03/26/2008 08:27 AM   Subject
> Re: BMC Remedy - Copy
> to Archive and Delete
> Please respond to   from Source
>arslist@ARSLIST.ORG
>
>
>
>
>
>
>
>
>
>
>
> **
>  Mel,
>
> I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
> those forms keeps performance at an acceptable level.  You have to
> remember
> that all workflow is affected by the number of records in the form and
> keep
> in mind any table fields that are refreshed.
>
> We generally keep 13 months of or closed records.
>
> Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
> option.  In the last month I've used it on HTs, Tasks and email messages.
> For us it appears to require a huge amount of disk space for the
> copy/delete option.  That needs to be planned for and it was greater than
> 1
> for 1 which is logical since another table is now holding the same record.
> For us it was quite a bit more than that infact we nearly brought the
> server down.
>
> I only archive in the lowest of production hours (night) when minimal
> users
> are on the system.
>
> I was also notified yesterday that it is not recommended to archive system
> email messages, there is some unusal result related to it.  Sorry did not
> get more info.
>
> I found the actual archiving to go fairly quick, was doing about 70k
> records both times.  I liked the fact I didn't have to manually delete the
> records afterwards.
>
> hth,
> Susan
>
> ShopperTrak
>
> On Wed, Mar 26, 2008 at 8:28 AM, Melanie Snayer <[EMAIL PROTECTED]>
> wrote:
> **
> Hi Joe
>
> Thanks so much for this information. Would you perhaps b

Re: BMC Remedy - Copy to Archive and Delete from Source

[Jason Miller]

The agreement that I have had with the user community at a few places I have
worked is to always keep a full 12 months of Help Desk records.  So by the
time we are ready to do annual archiving we are close to 2 years worth (and
some times we don't archive right at a year).  This allows at least a full
year reports at any time.  We do roughly 180k Help Desk tickets a year.

We archive the old fashion way of exporting an arx file and deleting the
records.  If there is ever a need to report on old records we will restore
them in an another environment.  On Help Desk usually most of reports don't
go past 1 year and this keeps us from maintaining extra
servers/cost/workflow to keep a reporting server.

Another thing to keep in mind is what is an appropriate interval for the
form you are archiving.  You many not want to keep only a year of Change
Requests or other forms that support policies and/or regulatory compliance.
Maybe you want to keep 5 years for Change Request and never archive Account
Requests and user system access records (both custom modules).

HTH,
Jason

On Wed, Mar 26, 2008 at 2:13 AM, Melanie Snayer <[EMAIL PROTECTED]>
wrote:

> ** Hi Listeners
>
> We're experiencing performance issues especially when submitting
> incidents. Our initial plan was to archive calls that have been closed for
> more than 5 years but as a result of the performance issues we're having to
> considering archiving as soon as 1 year and 6 months after having gone-live.
> Well, archiving is just one of the options that we have resorted to along
> side the current ongoing perfomance tuning that we're doing.
>
> Can you guys give me examples of how you may have gone about archiving
> your data? Like what the archiving criteria is and whether your archiving
> was done as a result of performance issue or as standard procedure.
>
> Thanks
> Mel
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: BMC Remedy - Copy to Archive and Delete from Source

[Brian Goralczyk]

Honestly, I agree with Thad.  400k should not cause a significant
performance hit.  Depending on how many records you create in a day, it
might not be a bad idea to set up a scheduled task to reindex the database.
Your DBA's should be able to help you decide when and how to do that.

I agree that table refreshes and work flow are usually the issue with
performance.  Always always always run an activelink/filter/sql log for
every major operation independently.  One for opening a record.  One for
just opening a form.  One for saving a record.  One for modifying a record.
And it never hurts to run them for individual actions that are done
regularly.  I know it sounds like a pain, but you can really tune the heck
out of your system if you do this.  It will allow you to see what is running
and doesn't need to.  And it will also give you a really good understanding
of your system.

Archiving is great, but with a properly tuned and sized system, it probably
isn't needed as much as people think.

Another thing to consider which might or might not be in your control, is
the distance (number of hops) between client and server as well as server
and database.  I have seen some really ugly server - database connections.
As bad as the two not being in the same town much less datacenter.

All these are things that can negatively impact your performance.

HTH,

Brian Goralczyk

On Wed, Mar 26, 2008 at 1:42 PM, Thad K Esser <[EMAIL PROTECTED]> wrote:

> **
> Joe,
>
> Properly indexed and tuned 400,000 tickets on a form shouldn't be a
> problem.  To expand on what Susan indicated, nine times out of ten, the
> biggest cause of slowness when opening forms is table fields that are
> needlessly being refreshed.  Watch out for tables being refreshed on hidden
> tabs.  Have an active link that fires on Gain Focus (of that tab) AND also
> on Display, with a run if of ('Page Holder' = "Tab Name').  The one action
> would be the table refresh.
>
> Of course there are other causes for slowness on opening of forms, but
> I've found this is the most common, and typically the easiest to fix.  (oh,
> and be suspect of any active link that fires on all three of Window Open,
> Window Loaded, and Display - its probably running three times when you
> display a ticket).
>
> *Thad Esser*
> Remedy Developer
> "*Argue for your limitations, and sure enough, they're yours."*-- Richard
> Bach
>
>
>   *"Susan Palmer" <[EMAIL PROTECTED]>*
> Sent by: "Action Request System discussion list(ARSList)" <
> arslist@ARSLIST.ORG>
>
> 03/26/2008 08:27 AM   Please respond to
> arslist@ARSLIST.ORG
>
>To
> arslist@ARSLIST.ORG  cc
>   Subject
> Re: BMC Remedy - Copy to Archive and Delete from Source
>
>
>
>
> **
>  Mel,
>
> I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
> those forms keeps performance at an acceptable level.  You have to remember
> that all workflow is affected by the number of records in the form and keep
> in mind any table fields that are refreshed.
>
> We generally keep 13 months of or closed records.
>
> Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
> option.  In the last month I've used it on HTs, Tasks and email messages.
>  For us it appears to require a huge amount of disk space for the
> copy/delete option.  That needs to be planned for and it was greater than 1
> for 1 which is logical since another table is now holding the same record.
>  For us it was quite a bit more than that infact we nearly brought the
> server down.
>
> I only archive in the lowest of production hours (night) when minimal
> users are on the system.
>
> I was also notified yesterday that it is not recommended to archive system
> email messages, there is some unusal result related to it.  Sorry did not
> get more info.
>
> I found the actual archiving to go fairly quick, was doing about 70k
> records both times.  I liked the fact I didn't have to manually delete the
> records afterwards.
>
> hth,
> Susan
>
> ShopperTrak
>
> On Wed, Mar 26, 2008 at 8:28 AM, Melanie Snayer <[EMAIL PROTECTED]
> * <[EMAIL PROTECTED]>> wrote:
> **
> Hi Joe
>
> Thanks so much for this information. Would you perhaps be able to tell me
> whether there was a delay on saving Help Desk tickets before you archived?
>
> Regards
> Mel
>
>
> On 3/26/08, *Joseph Kasell* <[EMAIL PROTECTED]<[EMAIL PROTECTED]>>
> wrote:
> Mel,
>
> We're running 7.0.1 with ITSM 6.  We instituted archiving a little over a
> month ago, it was sorely needed, and it certainly has made a difference.
> Since Remedy was put into production 

Re: BMC Remedy - Copy to Archive and Delete from Source

[Melanie Snayer]

Hi Susan

Thanks so much for this info. What database are you running on and on what
platform?

Mel


On 3/26/08, Susan Palmer <[EMAIL PROTECTED]> wrote:
>
> ** Mel,
>
> I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
> those forms keeps performance at an acceptable level.  You have to remember
> that all workflow is affected by the number of records in the form and keep
> in mind any table fields that are refreshed.
>
> We generally keep 13 months of or closed records.
>
> Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
> option.  In the last month I've used it on HTs, Tasks and email messages.
> For us it appears to require a huge amount of disk space for the copy/delete
> option.  That needs to be planned for and it was greater than 1 for 1 which
> is logical since another table is now holding the same record.  For us it
> was quite a bit more than that infact we nearly brought the server down.
>
> I only archive in the lowest of production hours (night) when minimal
> users are on the system.
>
> I was also notified yesterday that it is not recommended to archive system
> email messages, there is some unusal result related to it.  Sorry did not
> get more info.
>
> I found the actual archiving to go fairly quick, was doing about 70k
> records both times.  I liked the fact I didn't have to manually delete the
> records afterwards.
>
> hth,
> Susan
>
> ShopperTrak
>
>
> On Wed, Mar 26, 2008 at 8:28 AM, Melanie Snayer <[EMAIL PROTECTED]>
> wrote:
>
> > ** Hi Joe
> >
> > Thanks so much for this information. Would you perhaps be able to tell
> > me whether there was a delay on saving Help Desk tickets before you
> > archived?
> >
> > Regards
> > Mel
> >
> >
> >   On 3/26/08, Joseph Kasell <[EMAIL PROTECTED]> wrote:
> > >
> > > Mel,
> > >
> > > We're running 7.0.1 with ITSM 6.  We instituted archiving a little
> > > over a
> > > month ago, it was sorely needed, and it certainly has made a
> > > difference.
> > > Since Remedy was put into production back in the summer of 2004,
> > > approx
> > > 390,000 tickets had been submitted.  The amount of tickets had not
> > > been a
> > > problem until recently when we began to see performance lags
> > > performing
> > > various actions in Remedy.  Opening an existing Help Desk ticket from
> > > the
> > > Remedy Support console alone was taking anywhere from 1 to 5 seconds
> > > depending on the ticket (API and SQL logs were very helpful here).
> > >
> > > We decided to archive all Help Desk tickets with a status of Closed
> > > that
> > > were older than 13 months.  We considered using Remedy's archiving
> > > feature,
> > > but eventually went with Misi Mladoniczky's rrrchive utility.  Since
> > > our
> > > lab testing indicated that the archiving of an estimated 250,000
> > > tickets
> > > would take about 6 to 7 hours (and slow the system down tremendously),
> > > we
> > > decided to archive in chunks of 40,000 which limited the performance
> > > pain
> > > to about an hour.  We did this for 7 nights in a row.  I can tell you
> > > that
> > > since, performance has improved tremendously (max time to open an
> > > existing
> > > ticket is about a second).  Archiving is done nightly now.  It takes a
> > > minute to archive the 400 to 500 tickets that meet the archive
> > > criteria.  I
> > > know that my users are happy.
> > >
> > > Joe
> > >
> > > Joseph Kasell
> > > Navy Federal Credit Union
> > >
> > >
> > >
> > >
> > > Melanie Snayer
> > > <[EMAIL PROTECTED]
> > > MAIL.COM 
> > > >  To
> > > Sent by: "Action  arslist@ARSLIST.ORG
> > > Request System
> > > cc
> > > discussion
> > >
> > > list(ARSList)"Subject
> > > <[EMAIL PROTECTED] Re: BMC Remedy - Copy to Archive
> > > ORG>  and Delete from Source
> > >
> > >
> > > 03/26/2008 05:45
> > > AM
> > >
> > >
> > > Please respond to
> > > [EMAIL PROTECTED]
> > >RG
> > >
> > >
> > >
> > >
> > >
> > >
> > > --=_Part_6872_1105761.1206524742321
> > > Content-Type: text/plain; charset=WINDOWS-1252
> > > Content-Transfer-Encoding: quoted-printable
> > > Content-Disposition: inline
> > >
> > > Hey Thivagar
> > >
> > > We are in a 7.01 environment but I'm glad to know that this improved
> > > on
> > > performance. Could you perhaps give me a rough indication of the
> > > following information:
> > >
> > >   - what your database size is
> > >   - number of records before the archive
> > >   - time taken to save a call before the archive
> > >   - number of records after the archive
> > >   - time taken to save a call after the archive
> > >
> > > Anyone else like to share a bit of their archiving info with me?
> > >
> > > Regards
> > > Mel
> > >
> > > On 3/2

Re: BMC Remedy - Copy to Archive and Delete from Source

[Melanie Snayer]

Hey Chintan

Thanks for this info. As for your question, I have not come across any
documentation with information regarding max number of records in a table
and I doubt one would be released. The number of records that can be stored
in a form would depend on many different elements such as:

   - Number of and types of fields in the form
   - Number of forms in the database
   - Database size
   - Disk space
   - etc.

Regards
Mel


On 3/26/08, Chintan Shah <[EMAIL PROTECTED]> wrote:

> ** Mel,
>
> Last weekend we archived 120,000 records in less than 3 hours.
>
> We have 2 servers(production and reporting). Data gets DSO'ed from
> production to reporting all the time. So, we actually performed archivingon 
> reporting server.
>
> We only used "Copy to Archive" functionality. There was no performance
> impact whatsoever during the entire proecess.  I have not tested "copy to
> archive and delete from source" functionality.
>
> Our approach was like this
> 1. Take backup of all records you want to delete( in .arx file).
> 2. Have DBA take backup in a .dmp file.
> 3. Start "Copy to Archive" on the form you want to archive.
>
> Verify that we have same number of records(based on criteria u specify) on
> archived form as we have on source form.
>
> Now, the BIG part. We experience memory issues while deleting data using
> escalation.  One of our consultants proposed an excellent solution for
> deleting data.
>
> 1. Export only ID's of the records that you want to delete in .arx file.
> Use same criteria as you used for archiving.
> 2. Use a filter that fires on "Merge" and that performs an
> Application-Delete-Entry operation.
>
> This approach is as good as deleting 1 record at a time and has NO impact
> on server whatsoever.
>
> So, as soon as you start importing the data through "Remedy Import Tool",
> filter will fire and it will delete the record from production. As we have
> DSO in place, it will eventually delete from other server too.
>
> If you don't have separate reporting server, then you are pretty much done
> with process.
>
> It took almost 12:30 hours to delete all records with no user impact.
>
> By the way, I have a question. Is there any documentation available saying
> that "This is the max limit that Remedy can handle for good performance".
>
> Some of our forms have more than million records. Thanks for help in
> advance.
>
> Hope this helps.
>
> Thanks
> Chintan.
>
> *Joseph Kasell <[EMAIL PROTECTED]>* wrote:
>
> Mel,
>
> We're running 7.0.1 with ITSM 6. We instituted archiving a little over a
> month ago, it was sorely needed, and it certainly has made a difference.
> Since Remedy was put into production back in the summer of 2004, approx
> 390,000 tickets had been submitted. The amount of tickets had not been a
> problem until recently when we began to see performance lags performing
> various actions in Remedy. Opening an existing Help Desk ticket from the
> Remedy Support console alone was taking anywhere from 1 to 5 seconds
> depending on the ticket (API and SQL logs were very helpful here).
>
> We decided to archive all Help Desk tickets with a status of Closed that
> were older than 13 months. We considered using Remedy's archiving feature,
> but eventually went with Misi Mladoniczky's rrrchive utility. Since our
> lab testing indicated that the archiving of an estimated 250,000 tickets
> would take about 6 to 7 hours (and slow the system down tremendously), we
> decided to archive in chunks of 40,000 which limited the performance pain
> to about an hour. We did this for 7 nights in a row. I can tell you that
> since, performance has improved tremendously (max time to open an existing
> ticket is about a second). Archiving is done nightly now. It takes a
> minute to archive the 400 to 500 tickets that meet the archive criteria. I
> know that my users are happy.
>
> Joe
>
> Joseph Kasell
> Navy Federal Credit Union
>
>
>
>
> Melanie Snayer
>
> MAIL.COM > To
> Sent by: "Action arslist@ARSLIST.ORG
> Request System cc
> discussion
> list(ARSList)" Subject
>
> ORG> and Delete from Source
>
>
> 03/26/2008 05:45
> AM
>
>
> Please respond to
> [EMAIL PROTECTED]
> RG
>
>
>
>
>
>
> --=_Part_6872_1105761.1206524742321
> Content-Type: text/plain; charset=WINDOWS-1252
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> Hey Thivagar
>
> We are in a 7.01 environment but I'm glad to know that this improved on
> performance. Could you perhaps give me a rough indication of the
> following information:
>
> - what your database size is
> - number of records before the archive
> - time taken to save a call before the archive
> - number of records after the archive
> - time taken to save a call after the archive
>
> Anyone else like to share a bit of their archiving info with me?
>
> Regards
> Mel
>
> On 3/26/08, Thivagar Sankaran wrote:
>
> > **
> >
> > Hi Mel,
> >
> >
> >
> > Recently I have archived the data in my 6.3 environment. I have done
> this

Re: BMC Remedy - Copy to Archive and Delete from Source - AR System Email Messages?

[Nichols, Laura (Laura)]

Susan,
 
Can you elaborate on your statement, "I was also notified yesterday that
it is not recommended to archive system email messages, there is some
unusal result related to it."?  Do you remember where you got this
information?  Are you still archiving your email messages?
 
Anyone else heard or read anything on this??
 
Thanks,
Laura



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Wednesday, March 26, 2008 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source


** 
Mel,
 
I have found that for 'us' keeping less than 100k Help Tickets or Tasks
in those forms keeps performance at an acceptable level.  You have to
remember that all workflow is affected by the number of records in the
form and keep in mind any table fields that are refreshed.
 
We generally keep 13 months of or closed records.  
 
Since we upgraded to v7.0.1P3 last year I was excited about the
'archive' option.  In the last month I've used it on HTs, Tasks and
email messages.  For us it appears to require a huge amount of disk
space for the copy/delete option.  That needs to be planned for and it
was greater than 1 for 1 which is logical since another table is now
holding the same record.  For us it was quite a bit more than that
infact we nearly brought the server down.
 
I only archive in the lowest of production hours (night) when minimal
users are on the system.
 
I was also notified yesterday that it is not recommended to archive
system email messages, there is some unusal result related to it.  Sorry
did not get more info.
 
I found the actual archiving to go fairly quick, was doing about 70k
records both times.  I liked the fact I didn't have to manually delete
the records afterwards.  
 
hth,
Susan
 
ShopperTrak



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: BMC Remedy - Copy to Archive and Delete from Source - AR System Email Messages?

[James Van Sickle]

Laura

I tried to setup an Archive form for the Email Messages form a while ago,
and ran into the unusual activity that Susan was referring to.  Here is
what I wrote to the list a few months ago about it:

According to Remedy Support, creating an Archive Form for the AR System
Email Messages form causes a duplication of the reserved fields used by the
email engine to send email.  Apparently the email engine was not setup to
distinguish Field IDs such as 18085 between two separate forms.  When I
created an Archive form off the Email Messages form, the Email Engine
decided that my Archived Email Messages form was the new form to process
incoming and outgoing email on.  This became somewhat amusing as Incoming
email went directly to my Archive Form, and Outgoing email just sat in my
original Email Messages form waiting to get processed.

Removing the Archive form and restarting the Email Engine fixes the
problem.

(Embedded image moved to file: pic23851.gif)Countrywide


James Van Sickle
Remedy Developer II
Enterprise Service Management


 
 972-696-5779 Office  1000 Coit Road 
   92-540-5779Mail Stop: PCRD-2-19   
 Internal Plano, TX 75075
 






   
 "Nichols, Laura   
 (Laura)"  
 <[EMAIL PROTECTED]>  To 
 Sent by: "Action  arslist@ARSLIST.ORG 
 Request System cc 
 discussion
 list(ARSList)"Subject 
 <[EMAIL PROTECTED] Re: [ARSLIST] BMC Remedy - Copy to  
 ORG>  Archive and Delete from Source - AR 
   System Email Messages?  
   
 07/11/2008 12:06  
 PM
   
   
 Please respond to 
 [EMAIL PROTECTED] 
RG 
   
   




**
Susan,

Can you elaborate on your statement, "I was also notified yesterday that it
is not recommended to archive system email messages, there is some unusal
result related to it."?  Do you remember where you got this information?
Are you still archiving your email messages?

Anyone else heard or read anything on this??

Thanks,
Laura

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Wednesday, March 26, 2008 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source

**
Mel,

I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
those forms keeps performance at an acceptable level.  You have to remember
that all workflow is affected by the number of records in the form and keep
in mind any table fields that are refreshed.

We generally keep 13 months of or closed records.

Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
option.  In the last month I've used it on HTs, Tasks and email messages.
For us it appears to require a huge amount of disk space for the
copy/delete option.  That needs to be planned for and it was greater than 1
for 1 which is logical since another table is now holding the same record.
For us it was quite a bit more than that infact we nearly brought the
server down.

I only archive in the lowest of production hours (night) when minimal users
are on the system.

I was also notified yesterday that it is not recommended to archive system
email messages, there is some unusal result related to it.  Sorry did not
get more info.

I found the actual archiving to go fairly quick, was doing about 70k
records both times.  I liked the fact I didn't have to manually delete the
records afterwards.

hth,
Susan

ShopperTrak

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___

==

Confidentiality Notice:

Re: BMC Remedy - Copy to Archive and Delete from Source - AR System Email Messages?

[Mike White]

Just to share the other side

We started archiving 09/2006 while on ARS 6.0.1, patch 1497.  We're now
running 7.0.1, patch 7 (on Solaris 5.10, Oracle 10g).  We archive all Sent
messages, using Archive Type "Copy to Archive and Delete from Source",
daily @ 0700.  We've never had a problem with it.

Several years ago, we tried to archive user logins as we removed them and
ran into a reserved field id issue that sounds similar to what James
described.  We just haven't seen it on our email form.

Mike White
Office:  813-978-2192
E-mail:  [EMAIL PROTECTED]


   
  James Van Sickle 
  <[EMAIL PROTECTED]To:   arslist@ARSLIST.ORG
  RYWIDE.COM>cc:   
  Sent by: "Action       Subject:  Re: BMC Remedy - 
Copy to Archive and Delete from Source - AR System
  Request System  Email Messages?  
  discussion   
  list(ARSList)"   
  
   
   
  07/11/2008 13:28 
  Please respond to
  arslist  
   
   




Laura

I tried to setup an Archive form for the Email Messages form a while ago,
and ran into the unusual activity that Susan was referring to.  Here is
what I wrote to the list a few months ago about it:

According to Remedy Support, creating an Archive Form for the AR System
Email Messages form causes a duplication of the reserved fields used by the
email engine to send email.  Apparently the email engine was not setup to
distinguish Field IDs such as 18085 between two separate forms.  When I
created an Archive form off the Email Messages form, the Email Engine
decided that my Archived Email Messages form was the new form to process
incoming and outgoing email on.  This became somewhat amusing as Incoming
email went directly to my Archive Form, and Outgoing email just sat in my
original Email Messages form waiting to get processed.

Removing the Archive form and restarting the Email Engine fixes the
problem.

(Embedded image moved to file: pic23851.gif)Countrywide


James Van Sickle
Remedy Developer II
Enterprise Service Management



 972-696-5779 Office  1000 Coit Road
   92-540-5779Mail Stop: PCRD-2-19
 Internal Plano, TX 75075








 "Nichols, Laura
 (Laura)"
 <[EMAIL PROTECTED]>  To
 Sent by: "Action  arslist@ARSLIST.ORG
 Request System cc
 discussion
 list(ARSList)"Subject
 <[EMAIL PROTECTED] Re: [ARSLIST] BMC Remedy - Copy to
 ORG>  Archive and Delete from Source - AR
   System Email Messages?

 07/11/2008 12:06
 PM


 Please respond to
 [EMAIL PROTECTED]
RG






**
Susan,

Can you elaborate on your statement, "I was also notified yesterday that it
is not recommended to archive system email messages, there is some unusal
result related to it."?  Do you remember where you got this information?
Are you still archiving your email messages?

Anyone else heard or read anything on this??

Thanks,
Laura

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Wednesday, March 26, 2008 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source

**
Mel,

I have found that for 'us' keeping less than 100k Help Tickets or Tasks in
those forms keeps performance at an acceptable level.  You have to remember
that all workflow is affected by the number of records in the form and keep
in mind any table fields that are refreshed.

We generally keep 13 months of or closed records.

Since we upgraded to v7.0.1P3 last year I was excited about the 'archive'
option.  In the last month I've used it on HTs, Tasks and email messages.
For us it appears to require a huge amount of disk space for the
copy/delete option.  That needs to be planned for and it was greater than 1
for 1 which is logical since ano

Re: BMC Remedy - Copy to Archive and Delete from Source - AR System Email Messages?

[Nichols, Laura (Laura)]

James and Mike, thanks for the quick responses.  When our developer said
he "set up archiving" I thought he meant he was archiving data to an
archive form.  When I looked at the form I saw that he had set the
Archive type to "Delete from Source", so we won't have an archive form
after all...  



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mike White
Sent: Friday, July 11, 2008 12:35 PM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source - AR
System Email Messages?


** 

Just to share the other side

We started archiving 09/2006 while on ARS 6.0.1, patch 1497. We're now
running 7.0.1, patch 7 (on Solaris 5.10, Oracle 10g). We archive all
Sent messages, using Archive Type "Copy to Archive and Delete from
Source", daily @ 0700. We've never had a problem with it.

Several years ago, we tried to archive user logins as we removed them
and ran into a reserved field id issue that sounds similar to what James
described. We just haven't seen it on our email form.

Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
 James Van Sickle <[EMAIL PROTECTED]>



 



James Van Sickle
<[EMAIL PROTECTED]>
Sent by: "Action Request System
discussion list(ARSList)"  

07/11/2008 13:28
        Please respond to arslist



To: arslist@ARSLIST.ORG
cc: 
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source - AR
System Email Messages?  


Laura

I tried to setup an Archive form for the Email Messages form a while
ago,
and ran into the unusual activity that Susan was referring to.  Here is
what I wrote to the list a few months ago about it:

According to Remedy Support, creating an Archive Form for the AR System
Email Messages form causes a duplication of the reserved fields used by
the
email engine to send email.  Apparently the email engine was not setup
to
distinguish Field IDs such as 18085 between two separate forms.  When I
created an Archive form off the Email Messages form, the Email Engine
decided that my Archived Email Messages form was the new form to process
incoming and outgoing email on.  This became somewhat amusing as
Incoming
email went directly to my Archive Form, and Outgoing email just sat in
my
original Email Messages form waiting to get processed.

Removing the Archive form and restarting the Email Engine fixes the
problem.

(Embedded image moved to file: pic23851.gif)Countrywide


James Van Sickle
Remedy Developer II
Enterprise Service Management



972-696-5779 Office  1000 Coit Road
92-540-5779Mail Stop: PCRD-2-19
Internal Plano, TX 75075









"Nichols, Laura
(Laura)"
<[EMAIL PROTECTED]>
To
Sent by: "Action
arslist@ARSLIST.ORG
Request System
cc
discussion
list(ARSList)"
Subject
<[EMAIL PROTECTED] Re: [ARSLIST]
BMC Remedy - Copy to
ORG>  Archive and
Delete from Source - AR 

System Email Messages?


07/11/2008 12:06
PM


Please respond to
[EMAIL PROTECTED] 

RG







**
Susan,

Can you elaborate on your statement, "I was also notified yesterday that
it
is not recommended to archive system email messages, there is some
unusal
result related to it."?  Do you remember where you got this information?
Are you still archiving your email messages?

Anyone else heard or read anything on this??

Thanks,
Laura

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Wednesday, March 26, 2008 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: BMC Remedy - Copy to Archive and Delete from Source

**
Mel,

I have found that for 'us' keeping less than 100k Help Tickets or Tasks
in
those forms keeps performance at an acceptable level.  You have to
remember
that all workflow is affected by the number of records in the form and
keep
in mind any table fields that are refreshed.

We generally keep 13 months of or closed records.

Since we upgraded to v7.0.1P3 last year I wa