|
Comments
|
|
This was a great video. I would have liked just a little more information or explanation about the inefficient nested interation.
|
|
|
Loops are'nt necessarily inefficient. In some cases they are the best operator for the problem.
|
|
|
I enjoy watching the video. But, please, speak more slowly
and pronounce clearly the words, as I am not a native English speaker.
Thank you,
Nira G
|
|
|
Should be a little longer; I could use a suggestion of why would i want to use it.
Thanks Grant
Pat in NH
|
|
|
this video didn't do anything to explain what set up the nested loop.
|
|
|
It was short, laser specific, and gave good information, although it left me wanting a little more a blurb or two on perhaps other options when it is not the best thing due to larger returns.
|
|
|
This is the first time I've come across this series so I do not know what tools are being used and what the overall context of this unit is about. Particularly I want to know what IDE is being shown or where I can go for additional info. Thanks.
|
|
|
It would have been nice to hear an opinion around at what point does the dataset become to large for this to become inefficient.
|
|
|
Could have shown more of the code in the video. This way a person can follow along with an open query to pactice.
|
|
|
What alternative is there when working with a large number of records or a non-indexed field?
|
|
|
To everyone who thinks the video is too short... Yep. It's short. Sorry. That was the intent. A focused description of a single execution plan operator. It doesn't get into all the alternatives because it just wasn't supposed to. I'm working on some longer videos that will get into more extensive troubleshooting using execution plans.
|
|
|
To Richard Cook: This is the SQL Server Management Studio IDE. It's the management tool that comes with SQL Server 2008.
|
|
|
To Jonathan Winer: It really depends on the data involved. Good statistics on very large data sets could result in loop joins across hundreds or even thousands of rows.
|
|
|
To Jane Founfelker: There are two other basic join operators, and videos, Hash Match and Merge.
|
|
|
Well, you have defined something without explaining how the situation was created, or any alternatives. At the end of the clip, people who know what you are talking about will say "heh" and those who don't will say "huh?"
|
|
|
Excellent...Give us more about this kind.
Thanks.
|
|
|
that's great. can you have a series on execution plan from newbie to guru level, please?
|
|
|
Don Tulecki, basically it is the difference between:
1) 10 * 1000
vs.
2) 1000 * 1000
the 1) is the small hash with the large index. the 2) is the large loop in a large loop.
|
|
|
good, but could have been longer with more examples
|
|
|
would have been better to also show one that was inefficient.
|
|
|
It was a very clear headed representation of this structure.Which is better hash or nested
|
|
Deborah Land on
3/16/2010
Did a good job displaying the nested loop, but it didn't really explain to me what it was or how we got to it.
|
|
|
Did explain what a nested loop join is.
|
|
|
Like to see how to resove if the outer table contained a larger set of rows.
|
|
|
Very useful information
|