Are you archiving to the same server or a different server..?? Since you are mentioning DSO I'm assuming that it's a different server.
Either method works well - as long as it is architected to be "transaction aware" with the appropriate checks. I have the tendency to "over architect" data sync between systems to ensure there is no data-loss. For example: A pushes data to B B sends Delete to A It does not matter if this push is a push-fields / web-service / DSO / etc. The question that you need to also answer is the "readiness" of the data on the remote server. DSO queues up entries for processing, which is nice as it will handle it smoothly. A Filter/Web-Service ensures the data is "there now" so to say. HTH Robert On Fri, Aug 6, 2010 at 3:56 AM, Karen Doherty <[email protected]> wrote: > ** > > Good Morning, > > > > We are reviewing methods for archiving on a 7.1 server (Solaris10, Oracle > 10g) for a custom application - internal archiving vs DSO. I have used > internal archiving in the past and have had no issues with it, but I have > not used DSO for archving. > > > > According to a KM article, there is a chance of data loss if you use the > internal archiving. Has anyone had the same problem with DSO? What other > issues have you experienced? > > > > > > Karen > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ -- _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
