Lesson 3: Configuring Distribution
In this lesson, you will configure distribution at the Publisher and set the required permissions on the publication and distribution databases. If you have already configured the Distributor, you must first disable publishing and distribution before you begin this lesson. For more information, see Disabling Publishing and Distribution. Do not do this if you must retain an existing replication topology.
Configuring a Publisher with a remote Distributor is outside the scope of this tutorial.
Configuring distribution at the Publisher
Connect to the Publisher in SQL Server Management Studio, and then expand the server node.
Right-click the Replication folder and click Configure Distribution.
The Distribution Configuration Wizard launches.
On the Distributor page, select '<ServerName>' will act as its own Distributor; SQL Server will create a distribution database and log, and then click Next.
Enter \\<Machine_Name>\repldata in the Snapshot folder text box, where <Machine_Name> is the name of the Publisher, and then click Next.
Accept the default values on the remaining pages of the wizard.
Click Finish to enable distribution.
Setting database permissions at the Publisher
In SQL Server Management Studio, expand Security, right-click Logins, and then select New Login.
On the General page, click Search, enter <Machine_Name>\repl_snapshot in the Enter the object name to select box, where <Machine_Name> is the name of the local Publisher server, click Check Names, and then click OK.
On the User Mapping page, enable user mappings to both the distribution and AdventureWorks databases and add the users to the db_owner database role membership of these databases.
Click OK to create the login.
Repeat steps 1-4 to create a login for the local repl_logreader account. This login must also be mapped to users that are members of the db_owner fixed database role in the distribution and AdventureWorks databases.
Repeat steps 1-4 to create a login for the local repl_distribution account. This login must be mapped to a user that is a member of the db_owner fixed database role in the distribution database.
Repeat steps 1-4 to create a login for the local repl_merge account. This login must have user mappings in the distribution and AdventureWorks databases.