This is one of the best database sessions I have seen.Immensely in-depth analysis with lots of examples. I never knew the intricate details mostly the effect of index on concurrency. Additionally Brent is extremely engaging and makes the session indeed awesome.
I fully appreciate the things I'm learning from Brent. But this doubles as insane comedy. From 2:00 to 2:24 blocking is explained. And what follows is "The symptom of this is..." and I was thinking of what technicality might follow...but the next 6 words are amazing. I'm listening to this 20 times in a row and can't stop laughing.
Great ! I have been an Oracle DBA for two decades using Multi Version Read Consistency and was unhappy with statements / behaviours like "Readers Block Writers, Writers Block Readers" and "Microsoft automatically escalates locks".
@@BrentOzarUnlimited Can confirm here from The Netherlands... Been around since SS 6.5 as an application developer. A bit older and slightly grayer now, but still learning from your excellent "compelling to watch" videos. Thank you so much and good health to you!
like the video..................this is a keep..........................must know the two ways to overcome the blocks.....a) having enough indexes, and using the right Isolation for you app's....:) .....bye
In the video timeline at 22:40 the resource_type ="OBJECT" means the table but why are you telling it is clustered index as for resource type = "KEY" it is clustered index.
Наука
Brent has thought me so much with these videos and I've now started my training to become a DBA.
Thank you, good sir.
This is one of the best database sessions I have seen.Immensely in-depth analysis with lots of examples.
I never knew the intricate details mostly the effect of index on concurrency.
Additionally Brent is extremely engaging and makes the session indeed awesome.
Aww, thanks!
Thanks Brent. Used these techniques over the last few days to get to the bottom of and fix a deadlock without a NOLOCK in sight
Great presentation, Brent! Thanks for the detailed explanation on the internals.
just an awesome explanation! Funny and easy to understand!
This was very helpful and kind of liberating. Thanks .
Bob Ross of SQL!
Very nice explanation. Thanks Brent
Actually watching this on November 10th, 2022! 😂 What a coincidence. Well, happy birthday Brent! 🎉🎉🎉
Aww, thanks!
A great legend for SQL server...
I fully appreciate the things I'm learning from Brent. But this doubles as insane comedy. From 2:00 to 2:24 blocking is explained. And what follows is "The symptom of this is..." and I was thinking of what technicality might follow...but the next 6 words are amazing. I'm listening to this 20 times in a row and can't stop laughing.
I didn't remember what I said, so I had to listen to it, so now I'm laughing too.
Great ! I have been an Oracle DBA for two decades using Multi Version Read Consistency and was unhappy with statements / behaviours like "Readers Block Writers, Writers Block Readers" and "Microsoft automatically escalates locks".
YOU ARE KILLING ME WITH THE JOKES! THANKS FOR THIS VIDEO GREAT LESSON FOR ME!
HAHAHA, thanks.
@@BrentOzarUnlimited Can confirm here from The Netherlands... Been around since SS 6.5 as an application developer. A bit older and slightly grayer now, but still learning from your excellent "compelling to watch" videos. Thank you so much and good health to you!
Good presentation
The window in lower right-hand corner of you is covering the right side of the execution plan
Where’s this blog post he keeps referencing?
like the video..................this is a keep..........................must know the two ways to overcome the blocks.....a) having enough indexes, and using the right Isolation for you app's....:) .....bye
funny guy!
you should get an extra job in hollywood, for this joks
Awww yeah!
You sure hate Adventureworks or bicycles... I don't think you can stress it enough
As a wise woman once said, "Why not both?"
In the video timeline at 22:40 the resource_type ="OBJECT" means the table but why are you telling it is clustered index as for resource type = "KEY" it is clustered index.
The "KEY" part means it's only locking PARTS of the clustered index - not the whole thing.