My understanding was that if the isolation level on a connection was READ
COMMITED that a select statement would request locks with mode shared. But
when I run a simple select * from the query yzer, the locks generated
are intent-share and intent-exclusive. These intent-exclusive locks seem to
be setting us up for occasional deadlocks in our application. If they were
simply shared locks, the problem wouldn't be happening.
Also, in the Profiler, I can get info on object id on locks aquired but the
lock released info says nothing, so I can't really tell the duration of a