• 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,425 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,350 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.

(1)

You rated this post out of 5. Change rating

2019-08-14 (first published: )

38,470 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,644 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.

(7)

You rated this post out of 5. Change rating

2013-09-30

6,760 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,440 reads

Blogs

T-SQL Tuesday #198–Change Detection

By

This month we have a new host, Meagan Longoria, who graciously agreed to help...

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

Read the latest Blogs

Forums

Creating a JSON Document IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Creating a JSON Document IV

Permissions Removal When Changing Object Schema

By Brandie Tarvin

When the schema of an object is changed, SQL Server wipes out the previous...

Visit the forum

Question of the Day

Creating a JSON Document IV

I have this data in a table called dbo.NFLTeams

TeamID  TeamName       City             YearEstablished
------  --------       ----             ---------------
1       Cowboys        Dallas           1960
2       Eagles         Philadelphia     1933
3       Packers        Green Bay        1919
4       Chiefs         Kansas City      1960
5       49ers          San Francisco    1946
6       Broncos        Denver           1960
7       Seahawks       Seattle          1976
8       Patriots       New England      1960
If I run this code, how many rows are returned?
SELECT 
  YearEstablished,
  json_objectagg(city : TeamName)
FROM dbo.NFLTeams
GROUP BY  YearEstablished;

See possible answers