After Update Trigger

Question

0.00/5 (No votes)

See more:

SQL-Server

In After Update Trigger If their is any Update Statement for a same Table then is Trigger Fires Again

Posted 1-Oct-13 18:27pm

Member 9682127

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tejas Vaishnav · Answer 1 · 2013-10-01T18:38:00

Yes, it will fire the trigger in recursive mode.

I think this is not good idea to write code which will update the pointing table. if you miss any condition checking in trigger then it will be going to recursively firing the trigger and it will goes in infinite loop. so if there is no another way then this then you need to write your trigger in such a way to handle some cases when the trigger is not going to update the same table so it is the only way you stop the after update trigger to stop firing.