在SQL Server中使用镜像，日志传送，复制和群集的方案是什么 [英] What are the scenarios for using mirroring, log shipping, replication and clustering in SQL Server
问题描述
据我所知，SQL Server提供了4种技术以提高可用性。
As far as i know SQL Server provides 4 techniques for better availability.
我认为这些是主要的使用方案，总而言之：-
I think these are the primary usage scenarios, in summary :-
1）复制将主要适合在线-离线数据同步方案（笔记本电脑，移动设备，远程服务器）。
1) Replication would be primarily suited for online-offline data synchronization scenarios (laptop , mobile devices, remote servers).
2）日志传送可用于具有手动切换的故障转移服务器，而
2) Log shipping could be used to have a failover server with manual switching, whereas
3）数据库镜像是一种自动故障转移技术
3) Database Mirroring is an automatic failover technique
4）故障转移群集是数据库镜像的一种高级类型。
4) Failover Clustering is an advanced type of database mirroring.
Am i是吗？
谢谢。
推荐答案
故障转移群集是一项可用性技术在Windows群集技术的基础上构建的，可在硬件级别提供冗余，即它不是特定于SQL Server的。
Failover clustering is an availability technology that provides redundancy at the hardware level and is built on top of Windows Clustering technology, i.e. it is not specific to SQL Server.
例如，处理器在Server上崩溃答：幸运的是，服务器A是SQL Server群集的一部分，因此服务器B在几秒钟内就接管了提供SQL Server服务的工作。所有这些都是自动发生的，并且对集群服务的数据库用户和/或应用程序是透明的。
For example, the processor blows up on Server A. Fortunately Server A is part of a SQL Server Cluster and so Server B takes over the job of providing the SQL Server Service, within a matter of seconds. All of this occurs automatically and is transparent to the database users and or application being served by the cluster.
数据库镜像和集群之间的主要区别在于SQL集群提供了冗余在实例级别，而数据库镜像则在数据库级别提供冗余。
The main difference between Database Mirroring and clustering is that SQL Clustering provides redundancy at the instance level whereas database mirroring provides redundancy at the database level.
下面的链接提供了您可能会发现使用的这两种技术之间的比较。
The following link provides a comparison between these two technologies that you may find of use.
http://msdn.microsoft.com/en-us/library/ms191309 （SQL.90）.aspx
日志传送被认为更像是一种冗余技术。
Log shipping is considered more of a redundancy technology.
例如，它可以用于提供您的主要环境的完整副本，通常用作可以手动联机的热备份。这可用于为备份策略提供额外的冗余。
日志传送还可以通过在备用位置/服务器上创建生产数据库的只读副本来减轻主服务器的报告负担。
For example, it can be used to provide a full copy of your primary environment, typically used as a warm standby that can be manually brought online. This can be used to provide additional redundancy to your backup strategy. Log shipping can also be used to offload reporting from a primary server by creating a read only copy of the production database at an alternative location/server.
复制是一项非常多样化的技术，可以用来满足许多不同的场景，选择哪种场景将决定所实现的特定复制类型。
Replication is quite a diverse technology and can be used to cater for a number of different scenarios, the choice of which will determine the specific type of replication that is implemented.
例如，合并复制可通过在多个服务器（即分布式处理体系结构）上分散应用程序的工作负载来支持分布式处理。
For example, merge replication can be used to support distributed processing by spreading the workload of an application across several servers, i.e. distributed processing architectures.
合并复制通常需要相对了解其环境的应用程序。为了确保整个集成环境中的数据一致性，还必须考虑诸如冲突解决之类的技术。
Merge replication often requires an application that is relatively aware of its environment. Techniques such as conflict resolution also have to be taken into consideration in order to ensure data consistency across the entire integrated environment.
事务复制可以类似的方式用于记录日志。但是，您可以限制复制到订阅服务器的特定对象。如果仅出于报告目的只需要一部分表，这将很有用。
Transactional Replication can be used in a similar fashion to log shipping however you can limit the specific objects that are replicated to the subscriber. This can be useful if only a subset of tables is required for reporting purposes.
我希望这可以为您解决一些问题。您可以在SQL Server联机丛书中或通过在Google中搜索每种技术找到大量有关每种技术的文档。就是说，如果您有任何特定的疑问，我将很乐意为您提供帮助。
I hope this clears things up for you a little. You can find a wealth of documentation regarding each of these technologies within SQL Server books online, or by searching for each technology in Google. That said if you have any specific queries I would be happy to help so feel free to drop me line.
干杯，约翰
这篇关于在SQL Server中使用镜像，日志传送，复制和群集的方案是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
