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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote

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 (AT) hotmail (DOT) com> wrote