January 21, 2011 at 11:16 am
...this is also happening for SQL2008...
I know how to change the threshold in Replication Monitor to 'warn if latency exceeds the threshold', but even after saving the changes, the settings are only good for the period that Replication Monitor is active. That is, if I close the Monitor and reopen it, the settings go back to the default.
Seems like there should be a way to make the settings permanent...?
tia
February 10, 2011 at 8:21 am
As far as i know, the modifications you make in Replication Monitor are session based.
to make permanent, create an alert or two to manage replication latency
Performance conditions are:
MSSQL$MYINSTANCE:Replication Dist.|Dist:Delivery Latency
MSSQL$MYINSTANCE:Replication Logreader|Logreader:Delivery Latency
eg..
USE [msdb]
GO
/****** Object: Alert [distribution_latency] Script Date: 02/10/2011 15:18:30 ******/
EXEC msdb.dbo.sp_add_alert @name=N'distribution_latency',
@message_id=0,
@severity=0,
@enabled=1,
@delay_between_responses=180,
@include_event_description_in=0,
@category_name=N'[Uncategorized]',
@performance_condition=N'MSSQL$MYINSTANCE:Replication Dist.|Dist:Delivery Latency|SERVER\INSTANCE-PUB-SUB-SERVER\INST-11|>|150000',
@job_id=N'00000000-0000-0000-0000-000000000000'
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply