Initially the lecture was not impressive to me....looked like so regular things what he is discussing....many facts people might know....still I watched patiently till the end....where I got a clue to one of my production issue...a query was running much slow...when the lecture was on clustered index will do much better sometimes...and about creating indexes on text field...I thought of giving it a try...and tried creating an index ...which might go for clustered index seek for that text filed....it worked! The query which was running for nearly 9 sec to 17-18 seconds....came down to 3 to 8 seconds....mostly around 2-5 seconds which was our SLA for this application! Thanks for taking time to post this video! Much Appreciated!
This is a fantastic tutorial and would have made a great series. Sad to read that Doug moved on and that there will be no second part. Thanks for sharing this part nonetheless.
Clustered Index scan or index scan does not necessarily read entire rows of a table, it could be a range scan as well. If you hover the mouse over the operator you will see the description as (Scanning a clustered index, entirely or only a range). Here it pays much more attention to the cost of the operator but it is meaningless to the end user as it uses by the query optimizer to create the plan.
At the end of the video, you indicate there is another video with more operators like key lookup and join, but I do not see it in your video library. I'm quite sure you've got that content somewhere, I'm just not seeing it. Could you please point me in the right direction?
Sorry, we never built the second video. We stopped the project, but we wanted to upload this one for you so you could at least enjoy the completed one. Thanks!
Brent Ozar Unlimited NOOOOooooo! can you point me to a comprehensive source of all the execution plan steps explained? I’m diving into the deep depths of database operations, and am looking for good info
You need to put a table lock hint on the heap table when deleting rows or the empty data pages aren't returned to SQL Server. It's the storage equivalent of a memory leak.
The part where it got dark to show the table diagram freaked me out because I was watching the video at full screen. I thought my monitor was dying. :o
I have never heard "NVARCHAR" pronounced as 'en-vair-care'. Always (and in my mind) as 'en-vAr-CHar' where 'vAr' is pronounced like 'far' and 'char' is pronounced like 'CHARles'
Initially the lecture was not impressive to me....looked like so regular things what he is discussing....many facts people might know....still I watched patiently till the end....where I got a clue to one of my production issue...a query was running much slow...when the lecture was on clustered index will do much better sometimes...and about creating indexes on text field...I thought of giving it a try...and tried creating an index ...which might go for clustered index seek for that text filed....it worked! The query which was running for nearly 9 sec to 17-18 seconds....came down to 3 to 8 seconds....mostly around 2-5 seconds which was our SLA for this application! Thanks for taking time to post this video! Much Appreciated!
Amazing!!! The comparison visual towards the end was so simple yet powerful! Thanks a lot! :)
Very Nicely Explained . Was eagerly waiting for the other operators like Hash /Sort/Tables spool/Nested Loop/Compute Scalar etc...
best video i watched for execution plan operator
Wow this is by far the best clip explaining this stuff, thanks!
Exactly! Finally I understand this.
Thanks for making this wonderful video. So useful to get insight into those operators.
I have watched this more times than I can count over the last year. Excellent!
Excellent video! the best I have watched so far. Thanks a lot.
This is a fantastic tutorial and would have made a great series. Sad to read that Doug moved on and that there will be no second part. Thanks for sharing this part nonetheless.
Clustered Index scan or index scan does not necessarily read entire rows of a table, it could be a range scan as well. If you hover the mouse over the operator you will see the description as (Scanning a clustered index, entirely or only a range). Here it pays much more attention to the cost of the operator but it is meaningless to the end user as it uses by the query optimizer to create the plan.
Great stuff. Can't wait for part 2!
Very well done, easy to listen to and follow.
Amazing very useful ❤️
Thanks so much for the great video!
If I am not mistaken, you description of scans vs seeks is not consistent with what Brent Ozar himself says about them.
If he introduced himself as a stand-up comic, I wouldn't mind at all.
thank you sir
Most welcome
I liked the way he presented...straight to the point...Wondering why he didnot introduce himslef..
That's a class 🔥
Glad you enjoyed it!
When you end a video with "Coming up...", could you maybe please link to the next video in the description?
Thanks, and keep being awesome!
Kevin - unfortunately, Doug Lane left the company just after this video was filmed. We gave it away for the public anyway - hope you enjoy it.
At the end of the video, you indicate there is another video with more operators like key lookup and join, but I do not see it in your video library. I'm quite sure you've got that content somewhere, I'm just not seeing it. Could you please point me in the right direction?
Sorry, we never built the second video. We stopped the project, but we wanted to upload this one for you so you could at least enjoy the completed one. Thanks!
Brent Ozar Unlimited NOOOOooooo! can you point me to a comprehensive source of all the execution plan steps explained? I’m diving into the deep depths of database operations, and am looking for good info
@@narcissistectomy5134 no, sorry.
Yep, great video! When will the part 2 be released? Thanks
Hi! Unfortunately, there won't be a part 2 to this. Doug's moved on from the company. Thanks though!
Thats a shame! no one else on the Ozar team care to have a crack? This is the bees knees.
I did not understand what you saying about "heaps don't behave well when it comes to the deleted rows" please explain.
You need to put a table lock hint on the heap table when deleting rows or the empty data pages aren't returned to SQL Server. It's the storage equivalent of a memory leak.
sought on or seeked on, that is the question..
not surprised doug got head hunted after this
Yep, he's really sharp!
Best one
great video!
Thanks!
Yep, me too. Excellent video. Thanks you for doing it.
nice tutorial
thank you!
Thank's baby.
Brent is full of sass.
Superb Stuff !!!
Hey, thanks for the videos. The best SQL lesson I've learned in my life for sure. Thanks.
Where's the part 2? Anyone can drop me a link?
There won't be one - Doug moved on to another company.
Any link for the Part two video??
That's it for this series - you can find other courses at www.BrentOzar.com.
Where is the part 2?
That's it for this series - you can find other courses at www.BrentOzar.com.
Great video
Wait!! is he Brent Ozar?
The part where it got dark to show the table diagram freaked me out because I was watching the video at full screen. I thought my monitor was dying. :o
32:20
I have never heard "NVARCHAR" pronounced as 'en-vair-care'. Always (and in my mind) as 'en-vAr-CHar' where 'vAr' is pronounced like 'far' and 'char' is pronounced like 'CHARles'
Around here, we care about our data. We don’t burn (char) it.
Ok
This video is plain wrong.
Care to go into details?