This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
The RecursiveTriggers property controls nested call behavior for Microsoft SQL Server triggers.
If TRUE, a trigger can fire more than once when statement execution directs more than a single trigger execution. For example, a table T1 with trigger Trig1 may update table T2 with Trig2 enabled, which itself updates table T1. If the update of T1 directed by Trig2 causes modification that would normally fire trigger Trig1 and RecursiveTriggers is TRUE, trigger Trig1 fires a second time.
If FALSE, a trigger fires only once regardless of the actions of itself or other triggers enabled on other tables.