| title | MSSQL_ENG014150 | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/01/2017 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | replication | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | c3dd3109-abf3-4b38-a4e9-ef48d0235656 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| monikerRange | =azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allversions |
[!INCLUDEappliesto-ss-asdbmi-xxxx-xxx-md]
| Product Name | SQL Server |
| Event ID | 14150 |
| Event Source | MSSQLSERVER |
| Component | [!INCLUDEssDEnoversion] |
| Symbolic Name | |
| Message Text | Replication-%s: agent %s succeeded. %s |
This message indicates that a replication agent has successfully finished running. Replication uses the following agents:
-
The Snapshot Agent. This agent is used by all publications.
-
The Log Reader Agent. This agent is used by all transactional publications.
-
The Queue Reader Agent. This agent is used by transactional publications enabled for queued updating subscriptions.
-
The Distribution Agent. This agent synchronizes subscriptions to transactional and snapshot publications.
-
The Merge Agent. This agent synchronizes subscriptions to merge publications.
-
Replication maintenance jobs.
The Log Reader Agent, Queue Reader Agent, and Distribution Agent typically run continuously, whereas the other agents typically run on demand or on a schedule. If you do not expect an agent to have completed a run, check the status of the agent. For more information, see Monitor Replication Agents.
Replication Agent Administration
Errors and Events Reference (Replication)
Replication Distribution Agent
Replication Log Reader Agent
Replication Merge Agent
Replication Queue Reader Agent
Replication Snapshot Agent