Re: DISASTER RECOVERY
- From: Ekrem Önsoy <ekrem@xxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 22:15:59 +0200
Are your SQL Server servers in the same room? Do you need a real-time copy of your database? Do you need just a copy of your database or you want to use the secondary database?
Main difference between them is that Database Mirroring is a warm\hot standby and replication is a warm standby solution. Which means, Database Mirroring has a mode which provides you Automatic Failover (just like in Failover Cluster's but faster), but you must failover manually when you use Replication. Besides, as Database Mirroring' s Automatic Failover mode is a synchorous mode, it may slow your primary database if the link between the Primary Server and the Secondary Server is not good enough.
The only way to query a mirror database in Database Mirroring is using Database Snapshots (which is available in Developer, Evaluation and Enterprise Editions only) However you can query your secondary database in Replication.
It's easier to manage Database Mirroring than Replication.
--
Ekrem Önsoy
"Noor" <naissani@xxxxxxxxxxx> wrote in message news:%23yz$V3ViIHA.1944@xxxxxxxxxxxxxxxxxxxxxxx
I would appreciate if any one let me know which one is the best for disaster recovery and why.
Database Mirroring
Replication
I am using SQL Server 2005 and the application is mission critical. Please advice
Thanks
.
- References:
- DISASTER RECOVERY
- From: Noor
- DISASTER RECOVERY
- Prev by Date: Re: problem with connecting to sql server via a wireless applicati
- Next by Date: DISASTER RECOVERY
- Previous by thread: DISASTER RECOVERY
- Index(es):
Relevant Pages
|
