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 - 2003-12-30 : 12:10:37
|
| Keith writes "Your colleague at work has been collaborating with you on some slightly complex trigger designs. To track the execution path through the triggers during testing, your colleague has recommended adding RAISERROR('Useful comment here', 10, 1) WITH NOWAIT to each code branch in each trigger, to aid in testing from Query Analyzer. These statements will be removed prior to production deployment.You make the strange observation one day that the order in which the errors display is different on SQLDEV than on SQLTEST.You compare the SQLDEV and SQLTEST versions of the innards of each trigger using WinDiff, and the code is identical. The Table DDL, data content, and test inputs are identical. The OS, Data Access, and SQL Server versions and service packs on each SQL server are identical… The hardware is identical. The order in which the errors display is constant for each SQL Server, so random ordering is not at fault.What can possibly explain the cause for the order difference in which errors are displayed between SQLDEV and SQLTEST?Submitted byKeith BaugherKyle Tribble" |
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2003-12-30 : 12:10:38
|
| Is this within a single trigger or across multiple triggers? |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-12-31 : 07:23:46
|
| See sp_settriggerorder in bol.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Error Display Order