 | |
monitoring merge replication
microsoft.public.sqlserver.replication microsoft.public.sqlserver.replication
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
monitoring merge replication -
07-17-2003
, 02:50 AM
#2
| |||
| |||
|
|
this is a tricky one. When you expand your replication monitor folder in Enterprise Manager you will see a list of Replication Alerts. You can use these alerts to page you if a job fails. However, it is normal for replication jobs to fail and fail safe. On more complex environments these jobs are automatically restarted as many of the conditions which cause replication jobs to fail are network related, ie low bandwidth, or connection problems. Currently there is no thresh holds available in the alerting function, ie only send me a page if a job has failed 10 times in a row. You can query the MSdistribution_history table in your distibution database to get indications of how your distribution job is doing. You can set threshold on the results in this table, using your favorite programming language. -----Original Message----- Hi all, We have mssql2000 systems configured for Transactional replication and would like to automate the monitoring of successful replication process by sending a page to DBA support. Which table do i need to monitor or where could i get the success status of a replication process. . |
#3
| |||
| |||
|
|
-----Original Message----- As Hilary mentions this can be implemented out of distribution MSdistribution_history table. [runstats] column = 2 means it successfully finished. Comments can tell you about specific issues. MSrepl_error table can help as well. runstatus 1 = Start 2 = Succeed 3 = In progress 4 = Idle 5 = Retry 6 = Fail -- This posting is provided "AS IS" with no warranties, and confers no rights. OR if you wish to include a script sample in your post please add "Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm" AJM "Hilary Cotter" <hilaryK (AT) att (DOT) net> wrote in message news:097a01c34c5b$1a1f9c40$a401280a (AT) phx (DOT) gbl... this is a tricky one. When you expand your replication monitor folder in Enterprise Manager you will see a list of Replication Alerts. You can use these alerts to page you if a job fails. However, it is normal for replication jobs to fail and fail safe. On more complex environments these jobs are automatically restarted as many of the conditions which cause replication jobs to fail are network related, ie low bandwidth, or connection problems. Currently there is no thresh holds available in the alerting function, ie only send me a page if a job has failed 10 times in a row. You can query the MSdistribution_history table in your distibution database to get indications of how your distribution job is doing. You can set threshold on the results in this table, using your favorite programming language. -----Original Message----- Hi all, We have mssql2000 systems configured for Transactional replication and would like to automate the monitoring of successful replication process by sending a page to DBA support. Which table do i need to monitor or where could i get the success status of a replication process. . . |
#4
| |||
| |||
|
|
-----Original Message----- If you are using merge replication, you are going to want to look at the agent status in MSmerge_history, also found in your distribution database. Run the query below in your distribution db to get the most recent run status of your merge agent. Replace the data in angle brackets with your publication and subscription database names. declare @mergeid int declare @status int select @mergeid = id from MSmerge_agents where publication = <publication name> and subscriber_db = <subscription db select @status = runstatus from MSmerge_history where agent_id = @mergeid and time = (select Max(time) from MSmerge_history where agent_id = @mergeid) print @status JC -----Original Message----- As Hilary mentions this can be implemented out of distribution MSdistribution_history table. [runstats] column = 2 means it successfully finished. Comments can tell you about specific issues. MSrepl_error table can help as well. runstatus 1 = Start 2 = Succeed 3 = In progress 4 = Idle 5 = Retry 6 = Fail -- This posting is provided "AS IS" with no warranties, and confers no rights. OR if you wish to include a script sample in your post please add "Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm" AJM "Hilary Cotter" <hilaryK (AT) att (DOT) net> wrote in message news:097a01c34c5b$1a1f9c40$a401280a (AT) phx (DOT) gbl... this is a tricky one. When you expand your replication monitor folder in Enterprise Manager you will see a list of Replication Alerts. You can use these alerts to page you if a job fails. However, it is normal for replication jobs to fail and fail safe. On more complex environments these jobs are automatically restarted as many of the conditions which cause replication jobs to fail are network related, ie low bandwidth, or connection problems. Currently there is no thresh holds available in the alerting function, ie only send me a page if a job has failed 10 times in a row. You can query the MSdistribution_history table in your distibution database to get indications of how your distribution job is doing. You can set threshold on the results in this table, using your favorite programming language. -----Original Message----- Hi all, We have mssql2000 systems configured for Transactional replication and would like to automate the monitoring of successful replication process by sending a page to DBA support. Which table do i need to monitor or where could i get the success status of a replication process. . . . |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.