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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-01-04 : 09:31:01
|
| ariel writes "how can i manage that if i have 2 triggers that they would run with priority one after another" |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-01-04 : 09:49:22
|
| Check out sp_settriggerorder in BOL |
 |
|
|
sonmanvb
Starting Member
6 Posts |
Posted - 2002-01-04 : 11:32:53
|
| Does the sp_settriggerorder apply to sql 7.0, I found the topic in BOL for sql 2000 but not in bol for sql 7.0. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-01-04 : 14:38:25
|
| IMHO, the easiest way to ensure that trigger actions happen in the correct sequence is to put them all into one trigger in the proper sequence. It's easier to maintain, and when you think about it, an UPDATE or DELETE or INSERT is one operation, so having only one trigger for it makes sense (to me, anyway). |
|
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-01-04 : 18:56:09
|
I agree with Rob  . And to answer your question, NO in SQL 7 you cannot control which trigger fires first. All the more reason to follow Rob's advice.--------------------------------------------------------------1000 Posts, Here I come! I wonder what my new title will be... |
|
|
|
|
|
|
trigger priority