做最好的自己

我梦想终于有一天，我说服了我自己...

日志

AutoResetEvent

SQL Server Replication Step by Step

Sql Server Replication 简介

2008-08-12 09:39:19| 分类： SQLServer | 标签： |字号大中小订阅

reference：http://www.mssqlcity.com/FAQ/Replic/LinkSetRepl.htm

数据库复制技术：在LANs, WANs 或Internet上的相同或不同的服务器上的数据库对象的拷贝。

General Concepts

Publisher is the server or database that sends its data to another server or database.

Subscriber is the server or database that receives data from another server or database.

Distributor is the server that manages the flow of data through the replication system. This server contains the distribution database.

Publication is a collection of one or more articles that is sent to a subscriber server or database.Publisher contains publication/publications.

Article is the basic unit of replication and can be a table or a subset of a table.

Subscription is the group of data that a server or database will receive.

Push subscription is subscription when the publishing server will periodically push transactions out to the subscribing server or database.（Publisher->Subscriber）

Pull subscription is subscription when the subscribing server will periodically connect to the distribution database and pull information.（Subscriber->Publisher）

Distribution database is a system database, which is stored on the Distributor and does not contain any user tables. This database is used to store snapshot jobs and all transactions waiting to be distributed to Subscribers.

Replication topologies

Microsoft SQL Server supports the following replication topologies:

Central publisher
Central subscriber
Central publisher with remote distributor
Central distributor
Publishing subscriber

Central publisher 是最常用的拓扑结构。

Central publisher

Central subscriber 一般用于data wrehoursing。多个服务或数据库复制各自的数据到单一的服务或数据库中。

Central publisher with remote distributor 当复制操作比较频繁和重要，网络资源受限等情况下采用这种拓扑结构可以降低Publisher的负载，提高整个网络的通信流量。

Central publisher with remote distributor

Central distributor 这种拓扑最不常见，因为一旦dstributor服务器故障后，整个系统就无法工作了。

Central distributor

Publishing subscriber This is a dual role topology. In this topology, two servers publish the same data. One publishing server sends data to subscriber, and then this subscriber publish data to any number of other subscribers. This is useful when a Publisher should send data to Subscribers over a slow or expensive communications link.

Publishing subscriber

Replication types

Microsoft SQL Server supports the following replication types:

Snapshot 从Publisher完全拷贝数据到Subscriber，适合数据容量不是很大，变化比较频繁的场景。
Transactional 捕捉所有articles中的变化，存储Intert，Update， Delete等操作到distribution database，然后由distributor将更改发送到subscriber按序执行。适合数据容量较大，变化较频繁的场景。
Merge Merge replication is a most difficult replication type. It allows making autonomous changes to replicated data on the Publisher and on the Subscriber. With Merge replication, SQL Server captures all incremental data changes in the source and in the target databases, and reconciles conflicts according to rules you configure or using a custom resolver you create. Merge replication is best used when you want to support autonomous changes the replicated data on the Publisher and on the Subscriber.

Replication agents

Microsoft SQL Server 7.0/2000 supports the following replication agents:

Snapshot Agent
Log Reader Agent
Distribution Agent
Merge Agent

The Snapshot Agent is a replication agent that makes snapshot files, stores the snapshot on the Distributor, and records information about the synchronization status in the distribution database. The Snapshot Agent is used in all replication types (Snapshot, Transactional, and Merge replications), and can be administered by using SQL Server Enterprise Manager.

The Log Reader Agent is a replication agent that moves transactions marked for replication from the transaction log on the Publisher to the distribution database. This replication agent is not used in Snapshot replication.

The Distribution Agent is a replication agent that moves the snapshot jobs from the distribution database to Subscribers, and moves all transactions waiting to be distributed to Subscribers. The Distribution Agent is used in Snapshot and Transactional replications, and can be administered by using SQL Server Enterprise Manager.

The Merge Agent is a replication agent that applies initial snapshot jobs from the publication database tables to Subscribers, and merges incremental data changes that have occurred since the initial snapshot was created. The Merge Agent is used only in Merge replication.

评论这张

转发至微博

0人 | 分享到：

阅读(341)| 评论(0)| 引用 (0) |举报

AutoResetEvent

SQL Server Replication Step by Step

历史上的今天

this.p={  m:2,
              b:2,
              id:'fks_085067086083082075084080095095092087081067080086095068',
              blogTitle:'Sql Server Replication 简介',
              blogAbstract:'<P\>reference：<A rel=\"nofollow\" href=\"http://www.mssqlcity.com/FAQ/Replic/LinkSetRepl.htm\"  \>http://www.mssqlcity.com/FAQ/Replic/LinkSetRepl.htm</A\></P\>  <P\><A rel=\"nofollow\" href=\"http://www.mssqlcity.com/Articles/Replic/SetupSR/SetupSR.htm\"  \></A\> </P\>  <P\> 数据库复制技术：在LANs, WANs 或Internet上的相同或不同的服务器上的数据库对象的拷贝。</P\>  <P\><STRONG\><FONT color=\"#0000ff\" size=\"5\" \>General Concepts</FONT\></STRONG\></P\>  <P\><FONT size=\"2\" \><STRONG\>Publisher</STRONG\> is the server or database that sends its da<wbr\>ta to another server or database.<BR\><BR\><B\>Subscriber</B\> is the server or database that receives da<wbr\>ta from another server or database.</FONT\></P\>',
              blogTag:'',
              blogUrl:'blog/static/81004097200871293919951',
              isPublished:1,
              istop:false,
              type:0,
              modifyTime:1316917451249,
              publishTime:1218505159951,
              permalink:'blog/static/81004097200871293919951',
              commentCount:0,
              mainCommentCount:0,
              recommendCount:0,
              bsrk:-100,
              publisherId:0,
              recomBlogHome:false,
              attachmentsFileIds:[],
              vote:{},
              groupInfo:{},
              friendstatus:'none',
              followstatus:'unFollow',
              pubSucc:'',
              visitorProvince:'未设置',
              visitorCity:'未设置',
              postAddInfo:{},
              mset:'000',
              mcon:'',
              srk:-100,
              remindgoodnightblog:false,
              isBlackVisitor:false,
              isShowYodaoAd:false,
              hostIntro:'',
              hmcon:'0',
              lofter_single:'<a hidefocus="true" target="_blank" href="http://www.lofter.com/touch"><img onload="var nimg = new Image(); nimg.src=\'http://blog.163.com/newpage/images/analyse.png?lofter_single&t=\'+new Date().getTime()" border="0" src="http://b2.bst.126.net/newpage/images/lofter_single4.jpg"/></a>'
            }

{list a as x}
    {if !!x}
    <div class="iblock nbw-fce nbw-f40">
      <a class="fc03 noul" target="_blank" hidefocus="true" href="http://blog.163.com/${x.visitorName}/">
      {if x.visitorName==visitor.userName}
      <img alt="${x.visitorNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.visitorName)}&r=${visitor.imageUpdateTime}"/>
      {else}
      <img alt="${x.visitorNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.visitorName)}"/>
      {/if}
      </a>
      <div class="cwd vname thide">
        {if x.moveFrom=='wap'}
          <a class="noul pnt" target="_blank" href="http://blog.163.com/services/wapblog.html?frompersonalbloghome"><span title="来自网易手机博客" class="iblock wapIcon"> </span></a>
        {elseif x.moveFrom=='iphone'}
          <a class="noul pnt" target="_blank"><span title="来自iPhone客户端" class="iblock iphoneIcon"> </span></a>
        {elseif x.moveFrom=='android'}
          <a class="noul pnt" target="_blank"><span title="来自Android客户端" class="iblock androidIcon"> </span></a>
        {elseif x.moveFrom=='mobile'}
          <a class="noul pnt" target="_blank" href="http://blog.163.com/services/emsblog.html?frompersonalbloghome"><span title="来自网易短信写博" class="iblock wapIcon"> </span></a>
        {/if}
        <a class="fc03 m2a"  target="_blank" hidefocus="true" href="http://blog.163.com/${x.visitorName}/">
          ${fn(x.visitorNickname,8)|escape}
        </a>
      </div>
    </div>
    {/if}
    {/list}

<#--最新日志，群博日志--> <#--推荐日志-->

<p class="fc06">推荐过这篇日志的人：</p>
    <div>
      {list a as x}
      {if !!x}
      <div class="iblock nbw-fce nbw-f40">
        <a class="fc03 noul" target="_blank" hidefocus="true" href="http://blog.163.com/${x.recommenderName}/">
        <img alt="${x.recommenderNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.recommenderName)}"/>
        </a>
        <div class="cwd thide">
          <a class="fc03 m2a" target="_blank" hidefocus="true" href="http://blog.163.com/${x.recommenderName}/">
            ${fn(x.recommenderNickname,6)|escape}
          </a>
        </div>
      </div>
      {/if}
      {/list}
    </div>
    {if !!b&&b.length>0}
    <p  class="fc06">他们还推荐了：</p>
    <ul>
    {list b as y}
      {if !!y}
        <li class="rrb"><span class="iblock">·</span><a class="fc03 m2a" target="_blank" href="http://blog.163.com/${y.recommendBlogPermalink}/?from=blog/static/81004097200871293919951">${y.recommendBlogTitle|escape}</a></li>
      {/if}
    {/list}
    </ul>
    {/if}

<#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--相关文章--> <#--历史上的今天--> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->

页脚

公司简介 - 联系方法 - 招聘信息 - 客户服务 - 隐私政策 - 博客风格 - 手机博客 - VIP博客 - 订阅此博客

做最好的自己

导航

日志

Sql Server Replication 简介

Replication types

Replication agents

历史上的今天

相关文章

最近读者

评论

页脚