Hi,
It will be complicated to create identical Vendor forms in this way, or so
I would think.
If you really need to put it on a separate database, why not install a new
AR Server on that machine?
You can then use RRR|Chive to move records from your production server to
the archive server. I have done this in a number of cases, mainly before
the Archiving functionality was created.
In this case you can just import the same definitions you have in your
production environment, and reports etc will work for your archive server
as well as for your production server.
You can grant read-access for your users into the archive-server without
the need of costly write-licenses (fixed or floating).
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
* 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.
> hi Listers,
>
> We are trying to enable archiving on ARS 5.01. Yes we are aware that we
> dont
> have archiving functionality on ARS 5.0.1 (correct me if wrong). So here
> is
> how I am planning to do it and would like you guys to have a look at and
> with all the experience you have it will be great review.
>
> The purpose of archiving is to increase performance while searching and to
> reduce database size.
>
> Hence what I am suggesting is to create a new database with tables same as
> in AR database. (the T Tables). Then I will create vendor forms for all
> the
> forms that I need to archive and map them to the new database tables that
> I
> have created similar to the AR T tables using ARDBC plugin. Now I will run
> an esclation that will move the records from AR server forms to the new
> vendor forms by a special user AR_ARCHIVER just as it does with the
> inbuilt
> archiving.All other users will have only read only access to the archive
> form as per the inbuilt functionality.
>
> Now this will reduce the number of records on the AR Server forms and move
> it to the archive vendor form. (At least that is the idea)
>
> Now I am aware that I will need to keep an eye on all the changes that
> happens to the base form in terms of field addition and need to replicate
> on
> the vendor archive form. But thats ok with us as there wont be any change
> we
> guess.
>
> So let me know if you guys think this will work? I am currently trying for
> a
> small POC for the same will update for the same once I pass/fail and what
> would be the pros and cons for the same.
>
> Just trying to think OOTB :)
>
> Thanks,
> Viki
> --
> View this message in context:
> http://old.nabble.com/Data-Archiving-to-Vendor-form%21%21-will-it-work--tp30786586p30786586.html
> Sent from the ARS (Action Request System) mailing list archive at
> Nabble.com.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
