Nested Triggers

• Steve Jones - SSC Editor

  SSC Guru

  Points: 737630

  More actions

  December 14, 2022 at 12:00 am

  #4125096

  Comments posted to this topic are about the item Nested Triggers

• edwardwill

  SSCertifiable

  Points: 5911

  More actions

  December 14, 2022 at 8:13 am

  #4125359

  Can anyone imagine a scenario where such a catastrophic design decision was actually necessary?

• William Dunn

  SSC Veteran

  Points: 299

  More actions

  December 14, 2022 at 9:58 am

  #4125398

  Nightmare fuel, for sure!

• Steve Jones - SSC Editor

  SSC Guru

  Points: 737630

  More actions

  December 14, 2022 at 6:03 pm

  #4125609

  necessary, I'm not sure. I guess some auditing needs with relatively low workload. I wouldn't want a high insert/update level of batches if I had nested triggers.

  I, in general, try to avoid triggers as much as possible, because they are somewhat hidden. I wish that every table in SSMS/ADS and in every return message, we'd see a note that a trigger was fired. Something like:

  The command(s) completed successfully.

  2 rows updated (1 trigger fired)

  Or 2 triggers, or 10. The amount of time I've been confused by actions because I didn't think of triggers is far too high.

• edwardwill

  SSCertifiable

  Points: 5911

  More actions

  December 14, 2022 at 6:40 pm

  #4125639

  I worked at a software house where the rules were quite strict on triggers - they were not to be used.  So when we were getting glitches and couldn't work out what was happening, it took a long time to figure out that a rogue dev had added a (badly written) trigger.  Some kind of message, as you suggest, would be very helpful.