Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

FREE TRIALS

How are SQL Server DBSS Replication rule status levels collected? (4289710)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

How are SQL Server DBSS Replication rule status levels collected?
Description

For the Replication Agent, DBSS - Replication Agents - Status, from which SQL Server table is the data collected, which is responsible for the status and the severity information of the rule?
Also, we would like to know how is the mapping done for Critical, Warning and Normal Conditions like for e.g.
For Critical Condition:-
condition = ((#DBSS_status_severity_For_Rule#) == 3);
return Dbwc_Common_SQL_Server_IsNeedToSendAlarm(scope, "DBSS - Replication Agents - Status", "3", condition);
What same information is available for the rules DBSS - Replication Publications - Status and DBSS - Replication Subscriptions- status?
Resolution

For Replication Subscriptions, we use sp_replmonitorhelpsubscription
https://msdn.microsoft.com/en-us/library/ms188073.aspx
For the status from Replication Agents and Replication Publications we select the run_status FROM msdb..sysjobhistory joined with msdb..sysjobs on job_id.
This is a table with all available status and severity definition

Status Severity
Started Normal
Succeeded Normal
In progress Normal
Idle Normal
Completed Normal
Running Normal
Not Started Normal
Retrying Warning
Failed Critical

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Leave a Comment

Recommended Content

Product(s):: Foglight
6.1.0, 6.0.0, 5.9.8, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2, 5.7.5, 5.7.1, 5.6.11, 5.6.10, 5.6.7; Foglight for Databases
6.1.0, 6.0.0, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2

Topic(s):: Troubleshooting

Article History:: Created on: 11/15/2016
Last Update on: 5/7/2023

Search All Articles