|
Comments
|
|
Awesome.
|
|
|
interesting, never thought about what all goes on under the covers.
|
|
|
Excellent explanation of the complexity involved behind the scenes on something that appears simple
|
|
Lonnie Meinke on
3/26/2009
A little more setup would have been helpful.
|
|
|
How do I use this information for more efficient deletes?
|
|
Dennis Allen on
8/22/2011
I am a little fuzzy on the quiz stating that the clustered index delete is an operator...
|
|
|
Interesting, would have liked to have seen more detail.
|
|
|
would like to see a series of videos on query plans
|
|
|
Interesting, but not very useful to me
|
|
|
nice
|
|
|
a great tip
|
|
|
Little confused. The clustered delete operator indicates that a delete occurred. However, in reality the delete did not occur until the assert operator verifies. The actual delete will occur once the assert operator verifies that the FK constraints are not violated. Hence the reason for my answer.
|
|
|
Could have been more informational.
|
|
Maurice Ivory on
1/18/2012
It went just a little too fast for me...need about 1 more minute to explain the topic.
|
|
|
I have a question.
How I can delete automatically all rows after I execute report. I want clear the table when the raport is generated
|