镜像与复制 [英] Mirroring vs Replication

问题描述

如何决定在 SQL Server 2005 中选择复制还是镜像以同时提供数据可用性和性能.

How to decide whether to choose a Replication or Mirroring in SQL Server 2005 to provide data availabilty and performance at the same time.

为了更具体地说明我的 SQL 服务器架构，我有一个由 2 个节点组成的主动/主动集群，用于负载平衡，还有另一个用于复制的服务器，仅用于报告，我想做确定哪种技术最能同时提供可用性和性能，事务复制还是数据库镜像?

To be more specific about my SQL server architecture, I have an active/active cluster of 2 nodes which are used for load balancing, and I have another server for replication, which will be used only for reporting, I want to make sure which technology best provides both availabilty and performance, Transactional replication or Database Mirroring?

推荐答案

事实证明，数据库镜像会阻止直接访问数据，镜像数据只能通过数据库快照访问，因此快照数据的报告将无法达到因此，我将使用数据库事务复制来提供高可用性和负载平衡.

It turns out that Database mirroing prevents data to be accessed directly, mirrored data are only accessable through a database snapshot, so reports from snapshot data will not be up to date so, I will use Database Transactional Replication to provide high availabilit and load balancing.

这篇关于镜像与复制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！