Avoid cascading Triggers (SQL) | CAST Appmarq

Avoid cascading Triggers (SQL)


Rule Definition
Creating cascade in Trigger's execution can have unexpected results. Meaning having triggers that act on other tables in a way that causes triggers on that table to fire lead to obscure behavior. This behavior should be avoided.

Remediation
Review the design of the Triggers

Violation Code Sample
Example: 
Trigger_A is a trigger ON INSERT on the Table A 
Trigger_B which is a trigger of anytype is performing an INSERT on the same table Table_A therefore we consider that Trigger_B is cascading Trigger_A over Table_A

Related Technologies

Health Factor

  Total Quality Index


Technical Criterion
Complexity - Algorithmic and Control Structure Complexity

About CAST Appmarq

CAST Appmarq is by far the biggest repository of data about real IT systems. It's built on thousands of analyzed applications, made of 35 different technologies, by over 300 business organizations across major verticals. It provides IT Leaders with factual key analytics to let them know if their applications are on track.

Benchmark Statistics

Global Compliance

nan%

Total Violations
0
Total Opportunities
0
Average Violations / App.
nan
The compliance score represents 1 minus the ratio between the number of times a rule has been violated compared to the number of opportunities in a set of applications that the rule could have been violated.

Industry Insights

Financial Services

23.46%

Select from drop-down

93.80%

Software ISV

56.49%