May 11, 2012 at 7:43 am
dwain.c (5/10/2012)
Sean Lange (5/10/2012)
There was a story in another thread a few months ago by one of the regulars about a company that went belly up because their triggers couldn't handle multiple rows.
Sean - I would really like to read that article if you could find it.
We have an application that we support here and it ran up against just this issue. I hit upon the fact that ALL triggers should be able to support multiple rows (I call them bulk triggers) and not just single rows as a common sense thing without even the need to seek advice. Ultimately I went back through that app and rewrote every single bloody trigger in the thing to handle bulk ops.
The article would be useful to me to impress this point upon others not as enlightened.
For some I am thinking it was Brandie. I will ping the thread and see if anybody wants to come forward. It wasn't a story that had much more detail than what I posted but we will see what turns up. 😛
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply