Microsoft introduction to SQL Server replication-Overview of the replication publishing Model

Http://msdn2.microsoft.com/zh-cn/library/ms152567 (SQL .90). aspx

Replication uses publishing terminology to represent components in the replication topology, including the Publishing Server, distribution server, subscription server, publishing, project, and subscription. The magazine concept can be used to help you understand Microsoft SQL Server replication:

• Magazine publishers (publishing servers) produce one or more publications (publishing)
• Publication (publication) InclusionArticle(Project)
• Publishers (publishers) can issue (distribute) magazines directly or use Publishers (distribution servers)
• Subscriber (subscription server) receives subscribed publications (published)

Although magazine terms help to understand replication, it is important to note that the SQL Server replication package contains features not described in this term, especiallyFunctions of the subscription server to update and the function of the publisher to send incremental changes to the released Project.

The replication topology defines the relationship between the server and the data copy, and clarifies the logic that determines how data flows between the server. Several replication processes (called "proxies") are responsible for copying and moving data between the publisher and the subscription server. This is an overview of the components and processes involved in replication.

Publishing Server

A Publishing Server is a database instance that provides data to other locations through replication. The Publishing Server can have one or more releases. Each release defines a set of logically related objects and data to be copied.
 
Distributor

A distributor is also a database instance that acts as a storage zone and is used to copy specific data associated with one or more publishing servers. Each Publishing Server is associated with a single database (called a distribution database) on the distribution server. The distribution database stores the copy status data and metadata about the release, and in some cases it queues data that is moved from the Publishing Server to the subscription server. In many cases, a database server instance acts as a publishing server and a distribution server. This is called "local distribution server ". When the distribution server and the distribution server are configured according to their respective database server instances, the distribution server is called the remote distribution server ".

Subscription Server

The subscription Server is a database instance that receives replicated data. A subscription server can receive data from multiple publishing servers and publishing servers. Based on the selected replication type, the subscription server can also pass the data changes back to the publisher or re-publish the data to another subscription server.

Project

Project is used to identify database objects contained in a release. A release can contain different types of projects, including tables, views, stored procedures, and other objects. When a table is published as a project, you can use a filter to restrict the columns and rows of data sent to the subscription server.

Release

Publishing is a collection of one or more projects from a database. Grouping multiple projects into one release makes it easier to specify a group of database objects and data that are copied as a unit and have a logical relationship.

Subscription

Subscription refers to the request to pass the published copy to the subscription server. Subscription defines the time and place at which the subscription will be published and received. There are two types of subscription: Push and request. For more information about push subscriptions and request subscriptions, seeSubscribe to publishing.