Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sam_cit
Starting Member
2 Posts |
 Posted - 2009-01-29 : 06:47:54
|
| Hi, We have a use case where we have a update trigger on a table A. Now this trigger's action to update table B which in turn has a update trigger. The update trigger of table C goes on to update another table and this continues. Note that this is not recursive in nature just that many levels of triggers is invoked. As such, this is fine but the problem a single transaction of updating table A locks so many table for the entire team, which we are trying to avoid. Is there any other work around? Thanks in advance ! ! ! |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-01-29 : 06:55:18
|
See "Nested Triggers" and "Recursive Triggers" options at server and database level.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
sam_cit
Starting Member
2 Posts |
Posted - 2009-01-29 : 08:01:55
|
[quote]Originally posted by Peso
See "Nested Triggers" and "Recursive Triggers" options at server and database level. Hi, We don't run the limit of 32 for the nested triggers. In our case it is less than 10. However, the problem is that everything is a part of a single transaction which locks up all the tables and affects performance of other important transactions. So we are looking for a work around. |
|
|
|
|
|
|
Alternative to triggers invoking triggers