Skip to main content
added 29 characters in body
Source Link

You have 4 tables For transactional replication (push subscription) at the subscriber's side:

contains one row for each object that is associated with replication in the Subscriber database

contains one row of replication information for each Distribution Agent servicing the local Subscriber database

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssubscription-agents-transact-sql"

is used by Distribution Agent and triggers of updateable subscriptions to track subscription properties

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssnapshotdeliveryprogress-transact-sql"

is used to track files that have been successfully delivered to the Subscriber when a snapshot is being applied


you can use this columns to monitor the status for your replication at the subscriber's side

SELECT login_time,
       last_sync_status,
       last_sync_summary,
       last_sync_time,
       spid 
FROM dbo.MSsubscription_agents

You have 4 tables For transactional replication (push subscription) at the subscriber's side:

contains one row for each object that is associated with replication in the Subscriber database

contains one row of replication information for each Distribution Agent servicing the local Subscriber database

  • MSsubscription_agents

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssubscription-agents-transact-sql"

is used by Distribution Agent and triggers of updateable subscriptions to track subscription properties

  • MSsnapshotdeliveryprogress

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssnapshotdeliveryprogress-transact-sql"

is used to track files that have been successfully delivered to the Subscriber when a snapshot is being applied


you can use this columns to monitor the status for your replication at the subscriber's side

SELECT login_time,
       last_sync_status,
       last_sync_summary,
       last_sync_time,
       spid 
FROM dbo.MSsubscription_agents

You have 4 tables For transactional replication (push subscription) at the subscriber's side:

contains one row for each object that is associated with replication in the Subscriber database

contains one row of replication information for each Distribution Agent servicing the local Subscriber database

is used by Distribution Agent and triggers of updateable subscriptions to track subscription properties

is used to track files that have been successfully delivered to the Subscriber when a snapshot is being applied


you can use this columns to monitor the status for your replication at the subscriber's side

SELECT login_time,
       last_sync_status,
       last_sync_summary,
       last_sync_time,
       spid 
FROM dbo.MSsubscription_agents
Source Link

You have 4 tables For transactional replication (push subscription) at the subscriber's side:

contains one row for each object that is associated with replication in the Subscriber database

contains one row of replication information for each Distribution Agent servicing the local Subscriber database

  • MSsubscription_agents

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssubscription-agents-transact-sql"

is used by Distribution Agent and triggers of updateable subscriptions to track subscription properties

  • MSsnapshotdeliveryprogress

"learn.microsoft.com/en-us/sql/relational-databases/system-tables/mssnapshotdeliveryprogress-transact-sql"

is used to track files that have been successfully delivered to the Subscriber when a snapshot is being applied


you can use this columns to monitor the status for your replication at the subscriber's side

SELECT login_time,
       last_sync_status,
       last_sync_summary,
       last_sync_time,
       spid 
FROM dbo.MSsubscription_agents