Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Mirroring & Snap shot Replication

1 view
Skip to first unread message

Test

unread,
Apr 4, 2008, 1:10:03 PM4/4/08
to
Which one is better in terms of performance?

Database mirroring in 2005 or Snap shot replication in 2005

Please advice

Thanks in advance.

Ekrem Önsoy

unread,
Apr 4, 2008, 4:05:55 PM4/4/08
to
They are totally different stuff. Database Mirroring is used to keep a live
copy of your production database on another server. Aim of Database
Mirroring is High Availibility and Disaster Recovery, but the aim of
Snapshot Replication is some kind of copying your database for once and
can't be used instead of Database Mirroring for Mirroring is High
Availibility and Disaster Recovery purposes.

What are you needs?

--
Ekrem Önsoy

"Test" <te...@hotmail.com> wrote in message
news:0B07235E-5E16-46B4...@microsoft.com...

Test

unread,
Apr 4, 2008, 4:42:43 PM4/4/08
to
Sorry I used wronge name. Merge Replication.

In one of our environment we used Merge Replication and we want to used this
for Disaster Recovery as well, can't we use merge replication for disaster
recovery?

Please advince ..

"Ekrem Önsoy" <ek...@compecta.com> wrote in message
news:C2073D51-DBD9-444E...@microsoft.com...

Ekrem Önsoy

unread,
Apr 5, 2008, 4:26:38 AM4/5/08
to
Merge Replication' s purpose is to synchoronize (especially mobile) clients
and the server. It's a client->server \ server<-client topology. It's not a
design for a DR solution indeed.

So if you are looking for a DR solution, you should think of Log Shipping or
Database Morriring. Replication is an expensive solution and the best one
would be Transactional Replication if you insist on using Replication for DR
purposes. Of course, you should consider the network and IO while deciding
which one is the best for you. Otherwise you may have lots of headaches. For
example, if your network bandwidth between the primary server and secondary
server is a public network and not enough to send and recieve the data then
it's going to stuck one day. Same for the IO. These are important stuff to
take into account.

First, determine your needs and then consider your available hardware and
then choose the solution for yourself. Of course you can buy new stuff for a
better solution, it depends on your budget.

--
Ekrem Önsoy


"Test" <te...@hotmail.com> wrote in message

news:8CD5B172-C4DE-4A74...@microsoft.com...

0 new messages