> Patrick - you can place your agent job in a infinite loop.
> Have a second step which goes back to the first if the
> first fails. (see http://www.sqlmag.com/Articles/Index.cfm?
> ArticleID=19842)
> Regards,
> Paul Ibison

> Hi Patrick,
>
> No, you should not remove step 3. What Paul explained is that you should
> edit the properties of the "run agent" step to return to the first step in
> case of failure. To do this, go to the agent properties and edit the 'run
> agent' step. On the Advanced tab, change 'on success action'.
>
> The problem I see with that method is that you may not be notified if a
> serious problem occurs. The agent will just keep retrying and will never
> fail.
>
> Another option would be to change the agent schedule so that is doesn't
run
> continuously. If you have many replication agents, starting many agents
> simultaneously can cause performance problems.
>
> Regards,
> Shirley
> SQL Server Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use. © 2001 Microsoft Corporation. All rights
> reserved.
>