Scaling Out the Distribution Database

Replication is a great technology for moving data from one server to another, and it has a great many configuration options. David Poole brings us a technique for scaling out with multiple distribution databases.

Upgrading Replication from SQL Server 2000 32-Bit to SQL Server 2008 64-Bit without re-initialization

In this article we summarized the experiences we gathered during the planning and upgrade of a customer's project. The customer is one of the largest retail shops in its area. Their architecture is made up of a main server, which is located at headquarters and hosts several hundred publications containing over a thousand articles. Regional stores are located all over the country acting as subscribers for the publications hosted on the main server. Based on the business needs and infrastructure limitations the customer set the following goals for the project:

Replication

Push vs. pull: Configuring SQL Server replication

Learn the difference between push and pull subscriptions and how to determine the best placement for SQL Server replication's Distribution Agent

Peer-to-Peer Replication in SQL Server 2008 – Add a node and resolve conflict

Add a third node to a two-node Peer-to-Peer replication topology and learn how to resolve an update-update conflict.

Peer-to-Peer Replication in SQL Server 2008 – Configure a two-node topology

The first installment of this series describes the steps to configure a two-node Peer-to-Peer replication topology.

Replication

replication

CHECK CONSTRAINT

Getting additional error messaging information for SQL Server replication

When reviewing an issue through the Replication Monitor, the error messaging was leaving me wanting more detail to find out why the replication process was failing. So my question is, is there a way to garner more information from the replication agents running via SQL Server Agent?