Yes, that too... But all of the most powerful features can end up
causing problems, so I don't see how that's an issue. You can shoot
yourself in the foot with query hints, CLR executables, improper indexes,
and any number of other features, including triggers themselves!
Anyway, I was thinking it would be nice for two situations in
particular: A) Hierarchies (materialized path or nested sets), and B)
Programmatic concurrency control schemes -- both of which I use triggers
for, and both of which require you to deal with recursion, either by
disabling it entirely or doing checks...
SQL Server MVP - http://www.yqcomputer.com/
Author, "Expert SQL Server 2005 Development"