Home > Articles

SQL Server Transactional Replication Agents

If replication performance matters to you (and if you have the "honor" of maintaining replicated environments), you don’t want to miss this latest article by Baya Pavliashvili. Want to find out how replication agents work under the covers, how to tune agent's performance and log agents' output? Read on!
Like this article? We recommend

Like this article? We recommend

In my previous articles, I showed you how to configure, maintain, and troubleshoot transactional replication. This article digs a little deeper into issues associated with transactional replication agents. I'll discuss replication agents' properties as well as profiles. You'll learn how replication agents work under the hood and how you can tweak their parameters for performance tuning and troubleshooting.

Transactional replication is served by three agents. First, the snapshot agent takes the snapshot of the replicated articles (tables, views, stored procedures or user-defined functions) on the publisher. When you replicate tables, the snapshot agent creates the file containing the schema of the table, including any constraints, triggers, and indexes. The snapshot agent also creates the snapshot of any data contained in the tables. When you replicate non-table articles, the snapshot agent only scripts the schema of replicated objects.

The log reader agent scans the transaction log of the published database for any transactions affecting replicated objects; when such transactions are found, the log reader agent moves them into the distribution database.

The distribution agent reads replicated transactions in the distribution database and applies those transactions to the subscriber(s).

Let's look under the covers and see what each of these agents does more closely.

Snapshot Agent

You can examine the details of each replication agent by navigating to the Replication Monitor, selecting the publication you're interested in, right-clicking any of the agents, and choosing Agent Properties. A dialog box displays that shows you the properties of the SQL Server job associated with a particular agent, as shown in the following figure.

Figure 1Figure 1

If you examine the Steps tab of the snapshot agent job, you'll see that this agent is implemented by three steps. First, the agent runs the sp_MSadd_snapshot_history system stored procedure. This procedure is usually executed with the following parameters:

EXEC sp_MSadd_snapshot_history 
                        @perfmon_increment = 0, 
                        @agent_id = 10, 
                        @runstatus = 1, 
               @comments = 'Starting agent.'

The @perfmon_increment parameter is used to update replication performance counters for the agent associated with @agent_id; the latter is a reference to the id column in the MSsnapshot_agents table. Generic performance counter SQLServer:Replication Agents displays all replication agents that currently run on the server, whereas Snapshot:Delivered Cmds/sec and Snapshot:Delivered Trans/sec counters report the average number of commands and transactions delivered by the snapshot agent. In addition to updating the values of these performance counters, sp_MSadd_snapshot_history also records the history of the snapshot agent in the MSsnapshot_history table in the distribution database.

Not surprisingly, the @runstatus parameter determines the status of the snapshot agent; the following table lists the possible values for this parameter:

@runstatus Value



The agent is starting up


The agent has succeeded


The agent is in the process of executing


The agent is idle


The agent has encountered errors and is retrying its operations


The agent has failed

Finally the @comments parameter determines the message that is displayed in Enterprise Manager in the Last Action column of the snapshot agent.

So the first step simply updates performance counters and displays the snapshot agent's startup message. The next step is called Run Agent; this is the step that actually executes the snapshot agent. Here is the typical command for running the snapshot agent:

-Publisher [D10ZF411] 
-PublisherDB [pubs] '
-Distributor [ D10ZF411] 
-Publication [pubs1] 
-DistributorSecurityMode 1

This command advises the snapshot agent to use the D10ZF411 server both as publisher and distributor, to read the pubs1 publication within the pubs database, and to impersonate the SQL Server agent account when connecting to the publisher (security mode = 1). The security mode of 0 would advise the snapshot agent to use a SQL Server login for connecting to the publisher.

If the second step runs successfully, the entire job completes reporting success. If the second step fails, the snapshot agent must have encountered problems, so the last step (detect non-logged agent shutdown) is activated. This last step of the snapshot agent runs the sp_MSdetect_nonlogged_shutdown stored procedure within the distribution database. The sp_MSdetect_nonlogged_shutdown procedure is executed if the snapshot, distribution, or log reader agent encounters problems. This procedure attempts to detect the cause of the agent's failure and reports an appropriate message within the Replication Monitor, as well as within the job's history.

You can examine the job's history by right-clicking the job within Enterprise Manager and choosing View Job History. This applies to any SQL Server job, not just replication jobs. For example, the snapshot agent's job is likely to have a history similar to the following figure.

Figure 2Figure 2

Now that we've examined the details of the snapshot agent, we can learn more about the profile the runs this agent. Recall from my earlier article that the agent profile simply specifies the value of the parameters used for calling the replication agent.

The default values of the snapshot agent are explained in the following table.

Parameter Name

Default Value




Number of rows read by the snapshot agent in a single batch. Also the number of rows read/written before progress is reported within the Replication Monitor.



Amount of history logged. 0 is the least amount; 3 is the most.



Number of seconds the agent will attempt connecting to the publisher before timing out.



Number of threads a snapshot agent can use for scripting data and schema. A higher number of BCP threads typically means more parallel operations.



Number of seconds the agent will attempt to query replicated objects before timing out.

Query timeout and login timeout settings are fairly self-explanatory. If your agent can't log in to the server within 15 seconds, you obviously have a problem: Either your server is too busy to accept a new connection or you have specified invalid login credentials. If you can't run a particular snapshot agent query within 5 minutes (300 seconds), you're probably running the snapshot agent when the server is too busy performing other operations.

If possible, you should attempt to take the snapshot of the replicated objects during a period of little activity on the publishing server. If the publishing server must be available 24/7, and you can't afford lengthy downtime, you should consider alternative methods of delivering the initial snapshot. For example, you can simply back up the published database and restore it on the subscriber.

The history verbose level parameter is available for snapshot, distribution, and log reader agents. This parameter can either overwrite the existing values in the agent's history or create new records, thereby creating a more lengthy history. You should start with a detailed history logging to make sure that your replication setup works correctly. However, after you're certain that everything works as expected, you can get some performance advantage by reducing the history verbose level to 0.

The MaxBCPThreads parameter is available for snapshot agents as well as for distribution agents. This factor determines the number of parallel reads by the snapshot agent or parallel writes by the distribution agent when applying the snapshot at the subscriber. You can experience significant performance improvement on multiprocessor servers by bumping up the MaxBCPThreads option from its default value of 1. In my experience the MaxBCPThreads of 10 can work twice as fast as MaxBCPThreads of 1 on a 4-processor server. Note, however, that the number of parallel reads and writes you perform depends on the availability of CPU resources. If you have only a single CPU on your server, and CPU cycles are already tied up with other user activity, tweaking this option might not provide any performance benefit.

The BCPBatchSize parameter is the number of rows read or written by the snapshot or distribution agent within a single transaction and before the progress is reported within the Replication Monitor. If you have millions of rows to copy, you might want to increase the value of this parameter—this way the snapshot and distribution agents don't have to keep reporting progress and might work slightly faster.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020