at 10min when you were talking about the Update LCK type, it is not a deadlock, you are confusing it with a regular lock, a deadlock is when you have Two Transactions as in your case but let's assume that Tran01 wants to Update Tab1 and then Update Tab2 and Tran02 wants to Update Tab2 and then Update Tab1, you run both procedures or queries alongside and that is when you get a deadlock, at which point SQL Server kills one of those depending on a few criteria, your example when both Transactions are fighting solely on one resource (table in this example) is a regular lock which will just make the last transaction to ask for Update Lock to wait until the first finishes.
yes, you are right coz sql server introduced U lock, but the authoer was also right as he was explaining the scenario and assumed if there were no U lock in sql server, or why sql server introduced U lock
Simply Awesome,Words are not enough to congratulate you.Thanks a lot.Gaining More and more knowledge from your videos.Look forward for more which can be useful to DBA's.
Awesome video with good explanation on SQL Server Locks All Developers should know this much information and good refresh for DBAs. Narrator see to be very good at topic. I enjoyed watching this video and recommend others to watch. Thanks for educating the community and appreciate your efforts in publishing this video. Please keep publishing some more videos. Thanks a bunch
Hi, thanks for watching the video, please join www.techbrothersforum.com to ask any question that you may have. Tech Brothers and other professionals are online at the forum to help you out quickly. Thanks
Yeah, your description at 10min is totally wrong. This is not a Deadlock....this is a Blocking situation where 1 transaction will get the X lock, transaction 2 will wait (Blocked) until Transaction 1 is finished. Deadlocking is where Trans1 has a lock on Resource A and wants a lock on Resource B, and at the same time Trans 2 has a lock on Resource B and wants a lock on Resource A. One Trans will be killed in that situation. The situation you have drawn will not cause this situation. You should fix this video as Deadlocking and Blocking are 2 entirely different things.
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Too much knowledge to gain in 25 minutes. Great video 😊
at 10min when you were talking about the Update LCK type, it is not a deadlock, you are confusing it with a regular lock, a deadlock is when you have Two Transactions as in your case but let's assume that Tran01 wants to Update Tab1 and then Update Tab2 and Tran02 wants to Update Tab2 and then Update Tab1, you run both procedures or queries alongside and that is when you get a deadlock, at which point SQL Server kills one of those depending on a few criteria, your example when both Transactions are fighting solely on one resource (table in this example) is a regular lock which will just make the last transaction to ask for Update Lock to wait until the first finishes.
yes, you are right coz sql server introduced U lock, but the authoer was also right as he was explaining the scenario and assumed if there were no U lock in sql server, or why sql server introduced U lock
That's a really useful explanation. Thanks for taking the time to put it together.
Very useful to understand locking in SQL Server.. Thanks Tech Brothers..
Simply Awesome,Words are not enough to congratulate you.Thanks a lot.Gaining More and more knowledge from your videos.Look forward for more which can be useful to DBA's.
+Avinash Alladi Thanks very much for kind words dear!
Awesome video with good explanation on SQL Server Locks
All Developers should know this much information and good refresh for DBAs.
Narrator see to be very good at topic.
I enjoyed watching this video and recommend others to watch.
Thanks for educating the community and appreciate your efforts in publishing this video.
Please keep publishing some more videos.
Thanks a bunch
Hey u can join this one alao
You did great thank you for sharing
amazing. No one can beat you sir
+Rama Kambhampati :) Thank you so very much for kind words! I am very happy to know that you liked the tutorial.
your all videos are osm and really helping me in my training period!!
Glad to hear that our effort is helpful. Good luck!
You explained very well and simply. Thank you.
Hi, thanks for watching the video, please join www.techbrothersforum.com to ask any question that you may have. Tech Brothers and other professionals are online at the forum to help you out quickly. Thanks
Amazing video. That was really helpful
U r awesome
Another very informative video. Thank you so much.
THis made me clear. THank you very much
you are the best
That was really helpful. Thank you for sharing
You are most welcome. Thanks you watching.
Thank you for sharing your knowledge!
Ram Patel You are welcome Ram.
thank you
It's a really useful .
good explanation...Thank you
Excellent!! very helpful.
+James joy Thanks for watching!
Can you please explain basic difference between tablock and bulklock practically? I am bit confused in this so..
nice video. thank you so much
So is it safe to say that shared locks don't actually lock anything? They just let the DB that we are retrieving data from that resource?
nice video.. very informative
very helpful ,thank you
+H Saleh You are welcome and thanks for watching.
big thanks
Dead lock explanation is wrong
Excellent!
Thank you!
Good one
well explained :)
Yeah, your description at 10min is totally wrong. This is not a Deadlock....this is a Blocking situation where 1 transaction will get the X lock, transaction 2 will wait (Blocked) until Transaction 1 is finished. Deadlocking is where Trans1 has a lock on Resource A and wants a lock on Resource B, and at the same time Trans 2 has a lock on Resource B and wants a lock on Resource A. One Trans will be killed in that situation. The situation you have drawn will not cause this situation. You should fix this video as Deadlocking and Blocking are 2 entirely different things.
Really you confused me now.
It's not exactly the right model to explain a deadlock. :)
Sir you are too fast. You should speak slowly while teaching a particular topic
Useless and harmful material