August 1, 2013 at 10:18 pm
Comments posted to this topic are about the item Lock mode RangeI-N
Igor Micev,My blog: www.igormicev.com
August 1, 2013 at 11:29 pm
It's not an easy for me. but i got it correct.
Something new i learn today. Thanks π
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
August 1, 2013 at 11:53 pm
These are commonly knows as Range Locks
August 2, 2013 at 12:50 am
ashwani24 (8/1/2013)
These are commonly knows as Range Locks
(and If I recall correctly from my memory...) It applies for Serializable Isolation "only"
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
August 2, 2013 at 12:56 am
Danny Ocean (8/1/2013)
It's not an easy for me. but i got it correct.Something new i learn today. Thanks π
+1
First have to BOl about it before answering π
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
August 2, 2013 at 1:04 am
Stupid font (no offence to the question author). I started looking for RangeL-N. :crazy:
August 2, 2013 at 3:11 am
This was removed by the editor as SPAM
August 2, 2013 at 6:11 am
SQL Surfer '66 (8/2/2013)
Stupid font (no offence to the question author). I started looking for RangeL-N. :crazy:
+1 :doze:
_____________________________________________________________________
[font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]
August 2, 2013 at 7:13 am
Nice to see a question on locking - it would be good if technical internals stuff like this turned up more often in QOTD.
The lesson to be taken from the second reference given in the explanation is "avoid heaps, and really avoid heaps if you need serializable isolation". It's an interesting reference, and does involve I-N range locks, but not terribly relevant to the question. Perhaps a better second reference would be the SQL Server Transaction Locking and Row Versioning Guide which covers locking and versioning in versions from 2005 to 2012, but in fact the 1st reference in the explanation is perfectly adequate on its own.
edit: fix url tag
Tom
August 2, 2013 at 9:02 am
Danny Ocean (8/1/2013)
It's not an easy for me. but i got it correct.Something new i learn today. Thanks π
+1
August 2, 2013 at 9:51 am
Thanks for the lock question. I'd like to see more of these.
August 2, 2013 at 10:17 am
thanks for the question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 2, 2013 at 12:42 pm
Nice question igorMi and great explanation. I had not though about these types of locks for a while.
August 2, 2013 at 2:46 pm
L' Eomot InversΓ© (8/2/2013)
Nice to see a question on locking - it would be good if technical internals stuff like this turned up more often in QOTD.
+1 - We spent more than a month on locking protocols in our introductory DB class. Not information I use every day. BUT, knowing about it is good foundation information for the rest of what you need to know about databases.
Thanks to OP for question1
[font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
Connect to me on LinkedIn
August 3, 2013 at 12:12 pm
good question..
Thanks..
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply