Output from sp_help_rep_agent During Stream Replication

The output for sp_help_rep_agent when RepAgent is configured for Stream Replication to support synchronous replication in an HADR system for example, shows additional status information about the coordinator, scanner, and secondary truncation point manager processes that differ from the output when the replication mode is through log transfer language (LTL).

You can either execute sp_help_rep_agent without any parameter to show all information or execute sp_help_rep_agent with the process parameter to show only information about the processes.

Table 1: Column Descriptions for Output from sp_help_rep_agent with 'process' during Stream Replication
Column	Description
`<dbname>`	The name of the database for which you are querying process information.
`<pathname>`	The name of the replication path associated with each sender or scanner process if you configure multiple replication paths and scanners (multi-path Replication only).
`<spid>`	The system process ID of a process in the dataserver. For a Multithreaded RepAgent – spid identifies the coordinator task if you enable multiple scanners.
`<scanner_spid>`	The system process ID of each scanner process in the dataserver.
`<sender_spid>`	The system process ID of each sender process in the dataserver (not applicable for Stream Replication).
`<start marker>`	Identifies the first log record scanned in current batch.
`<end marker>`	Identifies the last log record to be scanned in current batch.
`<current marker>`	Identifies the current log record being scanned.
`<sleep status>` `<state>`	See the `<sleep_status>` and `<state>` columns together for the status of the coordinator, scanner, and secondary truncation point manager. Table : 2 Table : 3 Table : 4

When you enable the Stream Replication mode, see the <sleep_status> and <state> columns together for the status of the RepAgent coordinator, scanner, and secondary truncation point manager (Secondary Truncation Point Manager) threads and processes when you see the output from sp_help_rep_agent with or without the process parameter. Some of the statuses are tagged "rare" because they may appear very briefly as the process task moves from one common state to another and are therefore extremely unlikely to be seen.

Table 2: RepAgent Coordinator Process Status During Stream Replication
`<state>`	`<sleep status>`	Description
starting	not sleeping	Coordinator doing its own startup.
spawning	not sleeping	Coordinator is starting scanner or the Secondary Truncation Point Manager task.
spawning	sleep on task spawn	Coordinator is waiting on spawned task to indicate it has started.
running	updating mode	Coordinator is servicing a mode update.
running	not sleeping	Coordinator is otherwise working (rare).
sleeping	sleeping	Coordinator is waiting on alarm or event.
stopping	sleep on task terminate	Coordinator is waiting for scanner and Secondary Truncation Point Manager to stop.
stopping	not sleeping	Coordinator is shutting down (rare).

Table 3: RepAgent Scanner Process Status During Stream Replication
`<state>`	`<sleep status>`	Description
starting	not sleeping	Scanner is doing startup work (rare).
starting	opening stream	Scanner is sleeping, waiting on stream to open.
running	not sleeping	Scanner is working but not scanning (rare).
scanning	not sleeping	Scanner is actively scanning the log.
sleeping	stream sleep	Scanner is sleeping on a stream flush or package allocation.
sleeping	rewrite	Scanner is sleeping on a rewrite.
sleeping	sleeping	Scanner is sleeping on a dirty log.
sleeping	closing stream	Scanner is closing stream on shutdown.
sleeping	shutdown sync	Scanner is synchronizing with coordinator on shutdown (rare).
stopping	not sleeping	Scanner is shutting down (rare).

Table 4: RepAgent Secondary Truncation Point Manager Process Status During Stream Replication
`<state>`	`<sleep status>`	Description
starting	not sleeping	Secondary Truncation Point Manager is doing startup work (rare).
process trunc. point	not sleeping	Secondary Truncation Point Manager is processing a new truncation point.
running	not sleeping	Secondary Truncation Point Manager is working but not processing truncation points (rare).
sleeping	sleeping	Secondary Truncation Point Manager is waiting on an alarm or wakeup event.
stopping	not sleeping	Secondary Truncation Point Manager is stopping (rare).