Script to get a list of publications an article is in

Script to get a list of publications an article is in

Script to indentifty big replication transactions

Script to identify big replication transactions

Setting up Transactional Replication in SQL Server 2008 R2

Transactional Replication is used when DML or DDL schema changes performed on an object of a database on one server needs to be reflected on the database residing on another server. This article provides a step by step guide to setting up transactional replication on SQL Server 2008 R2.

Replication Schema Option Across Different Versions of SQL Server

My company uses replication quite extensively across SQL 2000, SQL 2005 and SQL 2008 servers. The problem with using different versions of SQL Server is that the replication options do not always behave the same way. Because of these differences we have stopped using SQL Server Management Studio and Enterprise Manager to setup replication. Also we have taken the time to look at the schema options for replication to make sure the end result is the same for all versions of SQL Server.

Using T-SQL to Verify Tables Row Counts in Transactional Replication

This article will help you to use T-SQL to verify that the Subscribers have the same number of rows of replicated data as the Publisher in transactional replication

6 Steps to setting up Replication with Mirroring

Script to setup transactional replication with updatable subscriptions when also using mirroring

Poor Man's Table Difference

Given a tablename and other parameters, this procedure will return a table made of foreign keys and a checksum for each

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