I'm currently experiencing problems with latency alerts on my transactional replication as described in this article:-
However, I'm at a loss as to what is meant in the workaround "1.Create a second identical alert that detects a smaller latency value (for example, 20,000 milliseconds). "
If I try and create a second alert, say using the following script:-
EXEC msdb.dbo.sp_add_alert @name=N'Replication Warning: Workaround for inaccurate latency reports',
@job_id=N'00000000-0000-0000-0000-000000000000' --insert job id for tracer token insertion here
I receive the following error:-
Msg 14501, Level 16, State 1, Procedure sp_add_alert_internal, Line 163
An alert ('Replication Warning: Transactional replication latency (Threshold: latency)') has already been defined on this condition.
Has anyone tried fixing this problem in this manner?
Follow me on twitter @EvoDBA
Check out my blog Natural Selection DBA