Blocking and Locking: How to Find and Fight Concurrency Problems

[@maskoblackfyre]

Brent has thought me so much with these videos and I've now started my training to become a DBA. Thank you, good sir.

[@sameersarmah1446]

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.

[@TheBrentOzar]

Aww, thanks!

[@steveearle9678]

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

[@oliviam.7139]

Actually watching this on November 10th, 2022! 😂 What a coincidence. Well, happy birthday Brent! 🎉🎉🎉

[@BrentOzarUnlimited]

Aww, thanks!

[@vchandm23]

Great presentation, Brent! Thanks for the detailed explanation on the internals.

[@George-iz2ce]

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.

[@TheBrentOzar]

I didn't remember what I said, so I had to listen to it, so now I'm laughing too.

[@ЕвгенийБогданович-ж7э]

just an awesome explanation! Funny and easy to understand!

[@wowDepressive]

This was very helpful and kind of liberating. Thanks .

[@Harshk2501]

Very nice explanation. Thanks Brent

[@gatlaaravind3178]

A great legend for SQL server...

[@antoniamesesan9711]

YOU ARE KILLING ME WITH THE JOKES! THANKS FOR THIS VIDEO GREAT LESSON FOR ME!

[@BrentOzarUnlimited]

HAHAHA, thanks.

[@marcokant5447]

@@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!

[@HemantKChitale]

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".

[@simonraaf7180]

Bob Ross of SQL!

[@mssrikanth8111]

Good presentation

[@drhdev]

Where’s this blog post he keeps referencing?

[@DaBadger354]

The window in lower right-hand corner of you is covering the right side of the execution plan

[@avinashrauniyar3784]

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.

[@BrentOzarUnlimited]

The "KEY" part means it's only locking PARTS of the clustered index - not the whole thing.

[@thunde7226]

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

[@ThamiSAOUDI]

you should get an extra job in hollywood, for this joks

[@BrentOzarUnlimited]

Awww yeah!

[@ariciupogoniciu4172]

funny guy!

[@jamirajamira7303]

You sure hate Adventureworks or bicycles... I don't think you can stress it enough

[@BrentOzarUnlimited]

As a wise woman once said, "Why not both?"