Enterprise Replication questions

I've been assigned the task of coming up with a way of not loosing a = single transaction in case of a physical disaster at the location of our database servers = (and backup servers). =20 To achieve this, I'm thinking of using ER in a many to one mode. That = is, replicating many database servers to one big off-site database server. Has anyone used ER in a many-to-one replication type? What are the = advantages or=20 drawbacks to using ER in this fashion? Terrence Mullins Sr Database Administrator www.WagerWorks.com

Using ER as a High availability solution with goal of not loosing single transaction in case of disaster is a bad idea. ER is asynchronies in its nature so you will have to take into consideration loosing some transaction. If you can't afford that use HDR, you can define several instances on one machine all are secondary to deferent machine. Uri Terrence Mu.... wrote: >I've been assigned the task of coming up with a way of not loosing a = >single transaction >in case of a physical disaster at the location of our database servers = >(and backup servers). =20 > >To achieve this, I'm thinking of using ER in a many to one mode. That = >is, replicating many >database servers to one big off-site database server. > >Has anyone used ER in a many-to-one replication type? What are the = >advantages or=20 >drawbacks to using ER in this fashion? > > > > >Terrence Mullins >Sr Database Administrator >www.WagerWorks.com > > > > > > > > > >