I see this lock being acquired after a merge statement on a table, as in the trace output I see a
RangeI-N lock on KEY: 7:72057594042515456
but if I run sp_lock inside a transaction in which I executed the merge (sp_lock after the merge, of course) I don't see the RangeI-N lock.
From the documentation I see that RangeI-N lock means: Insert range, null resource lock; used to test ranges before inserting a new key into an index.
So I'm wondering:
- is it a real lock that could potentially cause deadlocks?
- why is it not visible from sp_lock?