• Interests: SQL Server Performance and Code-Quality

Stairway to SQL Server Replication

Stairway to SQL Server Replication: Level 3 - Transactional Replication – The Publisher

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.

2023-01-04 (first published: )

11,457 reads

Stairway to SQL Server Replication

Stairway to SQL Server Replication: Level 2 - The Role of the Distributor

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.

2022-12-28 (first published: )

17,995 reads

Stairway to SQL Server Replication

Stairway to SQL Server Replication: Level 1 - Introduction to SQL Server Replication

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.

5 (1)

2019-08-14 (first published: )

36,610 reads

Stairway to SQL Server Replication

Stairway to SQL Server Replication: Level 4 - Transactional Replication – The Subscriber

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.

2013-12-11

12,243 reads

SQLServerCentral Article

The Fundamentals of SQL Server Replication by Sebastian Meine

Many of my clients need to make data that lives on one server available on another server. There are many reasons for such a requirement. You might want to speed up cross-server queries by providing a local copy of the data. Or you might want to make the data available to resource intensive reporting queries without impacting the OLTP load, maybe even with an intentional delay so you're always reporting against complete days only. Finally, you might be looking to implement high availability. In all these situations, SQL Server Replication is a viable option to look at when planning for the implemen­tation of such a requirement.

2 (7)

2013-09-30

6,466 reads

Blogs

RMOUG Training Days in Denver

By

Next week I’m heading to the Lowry Conference Center in Denver for the RMOUG...

Daily Coping 7 Feb 2023

By

Today’s coping tip is to go to bed in good time and allow yourself...

Tales From The Field Weekly Wrap Up for the Week of 01-31-2023

By

 Hello Dear Reader!  After a weekend with a lot of activities, it was a...

Read the latest Blogs

Forums

Modify RDS page missing the Storage Autoscaling option

By jecobdruv

Hi folks, I have a single Postgres instance on RDS that in the past...

how to make a col in a table after checking its existence, in one stmt

By rajemessage 14195

hi, IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME ='abc' AND COLUMN_NAME IN...

Coaching the Digital Transformation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Coaching the Digital Transformation

Visit the forum

Ask SSC Logo Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers