RE: deadlock in agent job

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Alejandro Mesa (AlejandroMesa_at_discussions.microsoft.com)
Date: 01/28/05


Date: Fri, 28 Jan 2005 09:25:02 -0800

Sorry, wrong place.

AMB

"Alejandro Mesa" wrote:

> This is normal behavior. A trigger is executed for each statement that causes
> the trigger to fire and not for each row affected by the statement. See
> "Multirow Considerations" in BOL.
>
>
> AMB
>
> "Randy" wrote:
>
> > I have a job with a single t-sql step. The tsql executes a stored proc that
> > occasionally deadlocks.
> >
> > I know i can't trap the deadlock in the stored proc, but I'd like to trap
> > the deadlock in the agent job, and retry the stored proc.
> >
> > What is the best way to handle this?
> >
> > -Rand y
> >
> >
> >



Relevant Pages

  • deadlock in agent job
    ... occasionally deadlocks. ... I know i can't trap the deadlock in the stored proc, ...
    (microsoft.public.sqlserver.programming)
  • RE: deadlock in agent job
    ... the trigger to fire and not for each row affected by the statement. ... > I know i can't trap the deadlock in the stored proc, ... > the deadlock in the agent job, and retry the stored proc. ...
    (microsoft.public.sqlserver.programming)
  • RE: deadlock in agent job
    ... > I know i can't trap the deadlock in the stored proc, ... > the deadlock in the agent job, and retry the stored proc. ...
    (microsoft.public.sqlserver.programming)
  • RE: Stored Proc doesnt work?
    ... use northwind ... > AMB ... the malfunctioning portion of a stored proc is below. ... >> SET NOCOUNT ON ...
    (microsoft.public.sqlserver.programming)