走进sql server 2005改进的负载平衡（Improved load balancing into SQL Server 2005）.docVIP

下载本文档

2
0
约 8页
2017-08-15 发布于河南
举报
版权申诉

走进sql server 2005改进的负载平衡（Improved load balancing into SQL Server 2005）.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

走进sql server 2005改进的负载平衡（Improved load balancing into SQL Server 2005）

走进sql server 2005改进的负载平衡（Improved load balancing into SQL Server 2005） SQL Server 2005 still does not support load balancing outside the machine - but it does provide some exciting improvements to support all the available load balancing methods in the previous version of SQL Server. I have described the load balancing method of SQL Server 2000 in my previous article. Here, Ill briefly introduce the following new features of SQL Server 20005: Table of contents Transactional replication of the P2P topology Table partition Backup and recovery improvements (fragment recovery) Database mirroring and snapshots Transactional replication of the P2p topology In SQL Server 2005, replication of transactions is improved by supporting the P2P topology. SQL Server 2000 supports bidirectional replication, which allows two servers to publish and receive data from each other at the same time. The server can update the same shared data, but in such a topology, you are limited to two servers. Support for the P2P topology is the number of servers that do not limit the amount of published data that exchanges transactions between each other. Of course, transaction delays are increasing as the number of servers added to the issue increases. Even though there is no theoretical limit to the number of nodes in your P2P topology, it is only in a limited number of cases that an acceptable performance can be provided. Microsoft recommends maintaining at 12 or less than 12 points in order to optimize performance. However, the topology of P2P is a major step forward in SQL Server: now, multiple peer servers can exchange data and copy transactions to other publishers. This means that the received server will not be restricted to the main reporting environment. You can scatter servers around the world and share transaction loads. As the number of users increases, you just need to add another server to the pool. In addition to distributed load, this topology has also increased the availability; if