Thank you Klaus for doing this. There is one thing only that scares me : the query gets executed 43 sec with HashSpills (not optimal query execution plan), the same query - with updated statistics and a pretty execution plan - gets taken - 53 sec ))))
I have one question..How does SQl calcluate the number of rows/Cardianality if we are joining 2 tables with a where clause of some columnid = some columnid of other table...do statistics have info about that too ?
Hi, Great video but just one clarification. What you showed in the board, is the behaviour of an INNER JOIN, where values are only passed to the next operator if there is a match, this would be different for LEFT and RIGHT joins
Thank you Klaus for doing this. There is one thing only that scares me : the query gets executed 43 sec with HashSpills (not optimal query execution plan), the same query - with updated statistics and a pretty execution plan - gets taken - 53 sec ))))
Thank you for these excellent videos. I like the way you explain in each video with first a theory and then practical with examples.
I have one question..How does SQl calcluate the number of rows/Cardianality if we are joining 2 tables with a where clause of some columnid = some columnid of other table...do statistics have info about that too ?
Love his Handwriting
very helpful. Thanks for your videos
Hi klaus,
Very helpful video.
Can you please share the Quicke on topics Statistics and Execution plans specially.
Hi, Great video but just one clarification. What you showed in the board, is the behaviour of an INNER JOIN, where values are only passed to the next operator if there is a match, this would be different for LEFT and RIGHT joins
You forgot a 1 in the last hack bucket?
Interesting and learnful. Thank you!
Thank you sir. That was enlightening.
great post and teaching skills. Keep it up. thanks
Cant you put your hands down?
Thanks again. A bit too much detail in the very beginning.
أحمد حميد يسلم عليك