continuous replication

Hi,
I have managed to set up continuous replication. However , i found out that
when there error such as "general network error" the replication stopped.
In such cases , won't it automatically re-do the synchronization ? and is
there any way to allow auto-synchronization if the network becomes "alive"
again ?
btw i have set up replication alerts if the agent failed
appreciate ur advice
tks & rdgs
Message posted via http://www.droptable.com
Either have your agent run continuously and restart every 5 minutes, or have
the agent on failure loop back to step 1.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5a91e9a42b79b@.uwe...
> Hi,
> I have managed to set up continuous replication. However , i found out
> that
> when there error such as "general network error" the replication stopped.
> In such cases , won't it automatically re-do the synchronization ? and is
> there any way to allow auto-synchronization if the network becomes "alive"
> again ?
> btw i have set up replication alerts if the agent failed
>
> appreciate ur advice
> tks & rdgs
> --
> Message posted via http://www.droptable.com
|||Hi ,
Curently this is how the flow for the continuous replications works
1)Distribution Agent startup mesage , on success --> go to next step , on
failure --> go to next step
2)Run agent , on success -->
quit with success , on failure --> go to next step ( but have specified to
retry 10 times btw an interval of 1 mins)
3)Detect nonlogged agent shutdown, on success --> Quit with failure , on
failure --> quite with failure
from ur suggesstion of "having the agent loop back" at which step shld the
loopback occur and MUST all the steps ( 1 - 3) be performed ?
i am thinking of if step 2 fails , then i'll loop back to step1 but i am not
sure what step3 does or upon success from step2 , i can go to step3 ?
need ur advice
tks & rdgs
Hilary Cotter wrote:[vbcol=seagreen]
>Either have your agent run continuously and restart every 5 minutes, or have
>the agent on failure loop back to step 1.
>[quoted text clipped - 11 lines]
Message posted via http://www.droptable.com
|||step 3 on failure should loop back to step 1
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:5a929eb6fdf53@.uwe...
> Hi ,
> Curently this is how the flow for the continuous replications works
> 1)Distribution Agent startup mesage , on success --> go to next step , on
> failure --> go to next step
> 2)Run agent , on success -->
> quit with success , on failure --> go to next step ( but have specified to
> retry 10 times btw an interval of 1 mins)
> 3)Detect nonlogged agent shutdown, on success --> Quit with failure , on
> failure --> quite with failure
> from ur suggesstion of "having the agent loop back" at which step shld
> the
> loopback occur and MUST all the steps ( 1 - 3) be performed ?
> i am thinking of if step 2 fails , then i'll loop back to step1 but i am
> not
> sure what step3 does or upon success from step2 , i can go to step3 ?
> need ur advice
> tks & rdgs
> Hilary Cotter wrote:
> --
> Message posted via http://www.droptable.com
|||tks for ur advice i'll try it out
Hilary Cotter wrote:[vbcol=seagreen]
>step 3 on failure should loop back to step 1
>[quoted text clipped - 29 lines]
Message posted via http://www.droptable.com