Read more...

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

Read more...

This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.  Read more...

I have noticed that available disk space on my SQL Server is getting low and I see a number of files getting generated in the replication snapshot folder. Because of these files there is a space issue on my server. Why are these files here and what can I do to resolve this problem?  Read more...

Read more...

This article demonstrates how to prevent primary key violation issues in transactional replication.  Read more...

This article provides a practical example of minimizing the growth of a distribution database.  Read more...

This article looks at the distribution database what information can be obtained for monitoring transactional replication.  Read more...

The Subscriber is the server where all the changes that are published by replication get delivered to. Every publication needs to have at least one subscriber, but a publication can have many subscribers. This level assumes that you have followed the first three levels and that you have a publication set up, to which you can subscribe.  Read more...

The Publisher is the database where all replicated data originates. Each Publisher can have multiple publications defined within it. Each publication contains a set of articles that all need to reside in a single database. Each article corresponds to all or part of a single database object. A single database object can map to an article in more than one publication.  Read more...

In this Stairway, Sebastian will be covering the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored.   Read more...

This article describes a design pattern for storing “effective dated" changes to fact tables.  Read more...

Script to get a list of publications an article is in  Read more...

Script to identify big replication transactions  Read more...

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.  Read more...

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.  Read more...

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  Read more...

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

Read more...