On Oct 8, 3:31 pm, SWrobel <swro...@gmail.com> wrote:
> I have a table with an After Insert trigger on it, which I believe
> means should only execute the trigger after the row has already been
> inserted in the table, however when the trigger fails, the row does
> not get inserted in the table. If it helps, the trigger is failing
> because it is calling a function that doesn't exist). I have fixed
> the problem, but was disturbed to find out that it was preventing
> inserts.

>I have a table with an After Insert trigger on it, which I believe
> means should only execute the trigger after the row has already been
> inserted in the table,

On Oct 9, 1:17 pm, SWrobel <swro...@gmail.com> wrote:
> On Oct 8, 2:01 pm, "Aaron Bertrand [SQL Server MVP]"
>
> <ten....@dnartreb.noraa> wrote:
> > >I have a table with an After Insert trigger on it, which I believe
> > > means should only execute the trigger after the row has already been
> > > inserted in the table,
>
> > An important component missing here is that it fires *before* the
> > transaction is committed. So, if there is a severe enough error in the
> > trigger, the transaction that caused the trigger to fire (e.g. the INSERT
> > statement) gets rolled back.
>
> Thanks for the replies, Alex and Aaron. Are you both saying that
> there is no way to force the transaction to commit even if the trigger
> has a fatal error?

<ten....@dnartreb.noraa> wrote:
> >I have a table with an After Insert trigger on it, which I believe
> > means should only execute the trigger after the row has already been
> > inserted in the table,
>
> An important component missing here is that it fires *before* the
> transaction is committed. So, if there is a severe enough error in the
> trigger, the transaction that caused the trigger to fire (e.g. the INSERT
> statement) gets rolled back.