Skip to main content

SQL Server Replication - Replication Agents

My first post in my replication series gave a brief overview of replication, before I dive into setting up and configuring the different types of replication I wanted to look a little more closely at the respective agents and the role they play in the different types of replication.

Replication Agents

Snapshot Agent - usually resides on the distributor server, it is used in all types of replication. The Snapshot Agent makes a copy of the schema objects and the data in the tables to published and stores them in  snapshot files in the snapshot folder, information about the snapshot  is stored in the distribution database.
Log Reader Agent - This is used in transactional replication. The log reader agent monitors the transaction log of all databases involved in replication. it monitors changes in the data marked for replication in the publication database's  transaction log and sends them to the distributor server. The transactions are held here until they are are ready to be sent to the subscribers.
Queue Reader Agent - is used with transactional replication and updateable subscribers publication type... The agent is run at the distributor and moves changes made at the subscriber back to the publisher.
Distribution Agent - is used in both snapshot and transactional replication. Its role is to move the snapshot and transactions stored at the distributor to the subscribing servers. In pull replication this agent lives on the subscribers and in push scenario it resides on the distributor server.
Merge Agent - surprisingly is used in Merge Replication. Unless you are using MERGE replication you will not be utilising this agent. This agent applies the initial snapshot to the subscriber servers. changes made after the initial synchronisation are monitored and merged to the subscribers ...This is the agent that is responsible for resolving update conflicts.


So these are the replication agents I will try and point out the how they work with each type of replication when we look at setting up and configuring replication.

Comments

  1. Gethyn:
    Good post. Thank you for sharing!!!

    ReplyDelete

Post a Comment

Popular posts from this blog

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

SQL Server Express v SQL Server Developer Edition

SQL Server Express v  SQL Server Developer Edition
Over the weekend I received the following in an email from Ali Ahmad who asked me some questions about learning SQL Server. We exchanged a couple of emails so I have boiled this down to the most salient points.

Question:
Goal: I want to learn SQL Server inside out… for career progression as DBA/BI/data mining. I'm a data analyst and want to learn inside out about data warehousing.
•I understand relational database concepts...
•I have SQL Server 2014 express installed…
•I need to download the adventure works sample in order to play with it.
•So much knowledge on Microsoft website it's easy to get lost… where do I begin?

SQL Server Express v SQL Server Developer
This is interesting. If you want to learn SQL Server inside out including the Business Intelligence suite of applications I would suggest downloading the developer edition of SQL Server which since 2016 has been made available free of charge. Prior to that there was a f…