|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 4:48 AM
Points: 282,
Visits: 116
|
|
Actually, Transactional Replication is running between Sql server 2005 to SQL Server 2000. But, Replication Status is running fine. all agents are running fine. but the subscriber end , tables are not updating.
when I checked, through Replication Monitor, I find a message..
'The initial snapshot for publication xxxx is not yet available'.
So I reinitialized and fix the problem.
But, I want a way to be informed , when such kind of msg, or obsolete snapshot msg is showing .
So I want to create a job to monitor those activity and in the above case the job use to send a mail to me.
Do any body have better solution to overcome this issue.????
Thanks in Advance.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 2:54 AM
Points: 1,076,
Visits: 5,128
|
|
Following may be better solution, still worth implementing: 1) You can create a job run Subscription Validation. 2) You can create alert for latency.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Friday, June 14, 2013 6:19 AM
Points: 340,
Visits: 459
|
|
| You can have a job at the publisher insert a tracer token periodically. If it doesn't arrive at the subscriber have a certain amount of time, the job can notify an operator to take a look for any replication errors or failures.
|
|
|
|