"Fei" <Fei@discussions.microsoft.com> wrote in message
news:6C2E0B93-453F-4A69-B0BD-577EF0C5BC92@microsoft.com...
> What's the best automated way to setup a disaster recovery environment in
> our
> situation?
>
> We have a production sql 2000 database receiving orders. If the machine
> crashes, we would like to use another server box to function ASAP (about
> 0.5
> to 1 hr latency is tolerable). Shall we setup a replication? What kind of
> replication model is good for our simple environment?

Hilary Cotter wrote:
> Replication is a solution for disaster recovery. The caveats with using it
> are no automated failover, and failback can be difficult. With
> bi-directional transactional replication failback is much easier.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "Fei" <Fei@discussions.microsoft.com> wrote in message
> news:6C2E0B93-453F-4A69-B0BD-577EF0C5BC92@microsoft.com...
> > What's the best automated way to setup a disaster recovery environment in
> > our
> > situation?
> >
> > We have a production sql 2000 database receiving orders. If the machine
> > crashes, we would like to use another server box to function ASAP (about
> > 0.5
> > to 1 hr latency is tolerable). Shall we setup a replication? What kind of
> > replication model is good for our simple environment?