High Availability: Interoperability and Coexistence

Database mirroring can be used with the following features or components of SQL Server:

• Change data capture (and change tracking)

• Failover clustering

• Log shipping

• Full-text catalogs

• Database snapshots

• Replication

Log shipping can be used with the following features or components of SQL Server: 

• Database mirroring

• Replication

Note

For a general comparison of the SQL Server high-availability solutions, see High Availability Solutions Overview.

In This Section

• Change Data Capture and Other SQL Server Features
  Contains information about using change data capture (CDC) with database mirroring.

• Database Mirroring and Failover Clustering
  Describes database mirroring as an easy-to-manage alternative to failover clustering. Database mirroring can be used between two different failover clusters, but not within a single cluster.

• Database Mirroring and Log Shipping
  Describes how a single database can be configured as the principal database in a mirroring session and also as the primary database in a log shipping configuration.

• Database Mirroring and Cross-Database Transactions
  Describes why database mirroring is not supported with either cross-database transactions or distributed transactions.

• Database Mirroring and Full-Text Catalogs
  Describes how to mirror a database that has a full-text catalog.

• Database Mirroring and Database Snapshots
  Describes how to create one or more database snapshots on a mirror database to permit clients to use the mirror database for limited report writing.

• Replication and Database Mirroring
  Describes the effects of log shipping on replication behavior and the requirements and procedures for replicating from the secondary if the primary is lost.

• Replication and Log Shipping.
  Describes the effects of log shipping on replication behavior and the requirements and procedures for replicating from the secondary if the primary is lost.