title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | monikerRange | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|
MSSQL_ENG014150 |
MSSQL_ENG014150 |
MashaMSFT |
mathoma |
09/25/2024 |
sql |
replication |
reference |
|
|
=azuresqldb-mi-current||>=sql-server-2016 |
[!INCLUDE SQL Server SQL MI]
Attribute | Value |
---|---|
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.