Hi,
How can I identify longers locks in a database?
is it possible to validates which locks (row, page or table level) will be used by specific queries / views? (is the execution plan identify this?)
the longer locks are too quick to be trapped using sp_locks.
I'll use the profiler to track the database activity,
but maybe there is a query which can be used in SQL to simplify this process and quickly identify the latest locks and the reasons (query locked vs query locking)