|
Comments
|
|
okkkkkkkkkk..........need more focus on this topic..........
|
|
|
It is good to see the difference, but it would be the best if the alternative solution was provided to make the actual execution plan easier. Grant Fritchey is one of the excellent author in this and i hope he will try to post the same.
|
|
|
The goal for all the short videos was just to define the issue, not offer up solutions. It works for some people and not for others.
|
|
Darren Bates on
6/18/2009
yes, but there's no explanation or comparison of other methods if you need the functionality of the trigger!
|
|
|
I understand and I couldn't possibly argue with you. You're right. None of that is there. But, none of that was supposed to be included. This was just supposed to be informational, "here's what happens with triggers." It's not trying to be judgemental about whether or not the trigger is good (in this case, I wrote a bad trigger on purpose, just to make it more obvious). I am going to try to record more videos when I can. I'll make the next ones longer and include more details, alternatives, solutions, etc.. We just weren't trying to do that with these videos.
|
|
A Alagu Ganesh on
10/14/2010
Good
|
|
|
ok
|
|
|
Yes. I agree that it is very very informative & basic. No alternative solution is provided. Those using the execution plans, & Performance tuning can easily makeout that it is a costly affair to do this way, so why need to see the video ?
|
|
|
too short, too little information, and not in context
|
|
|
Great quick informative about the hidden cost of an update trigger. Thanks Grant.
|
|
|
Very Interesting. Sharing w/ my coworkers
|
|
|
Nice trick for seeing the impact of a seemingly "simple" update that has a trigger!
|
|
|
OK, so triggers can be expensive... but we need to see the actual code of the example trigger and maybe improved versions of it to see how to mitigate the expense.
|