• 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.

You rated this post out of 5. Change rating

2023-01-04 (first published: )

12,281 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.

You rated this post out of 5. Change rating

2022-12-28 (first published: )

19,061 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)

You rated this post out of 5. Change rating

2019-08-14 (first published: )

38,181 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.

You rated this post out of 5. Change rating

2013-12-11

15,210 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)

You rated this post out of 5. Change rating

2013-09-30

6,542 reads

Stairway to SQL Server Replication

Stairway to SQL Server Replication - Level 7: Merge Replication – Subscription

This level of the Stairway will cover 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.

You rated this post out of 5. Change rating

2012-02-03

7,374 reads

Blogs

Copying an Azure SQL database between two Azure SQL Instances in two different subscriptions.

By

I recently had to copy an Azure SQL database (SQL db) from one subscription...

A field note: AI Ambition vs. Operational Reality in 2025

By

Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...

Redefining Tech Leadership in the Age of Microsoft AI

By

AI is no longer a niche capability – it is a leadership catalyst. As...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

SQL Server Columnstore Index Fragmentation

By Grant Fritchey

Comments posted to this topic are about the item SQL Server Columnstore Index Fragmentation

do i lose "what this object depends on" etc when moving sprocs to etl server

By stan

Hi i was surprised to see the approach my coworkers used to sunset talend...

Visit the forum

Question of the Day

SQL Server Columnstore Index Fragmentation

The columnstore index is absolutely different than the traditional rowstore b-tree index. Because of this, it doesn't suffer from the same kind of fragmentation across pages as the b-tree index. Yet, it does suffer from a type of fragmentation brought about by an excess of deleted rows in a rowgroup and a lack of compression of storage because more things are in the delta store. While b-tree indexes use dm_db_index_physical_stats to show fragmentation, which system tables or DMVs can be used in SQL Server (prior to SQL Server 2025) to determine columnstore fragmentation?

See possible answers