June 11, 2003 at 7:35 am
Does read uncommitted take any locks on objects beyond schema locks? I have some long running stored procedures and I'm thinking about setting the isolation level to read uncommitted. I don't want these sprocs to issue any locks on any data.
I don't think it is possible but here's a follow up question - any ideas on how to set it so that it will not issue any locks but would honor all locks set by other transactions.
June 11, 2003 at 5:49 pm
No it avoids the locks. However it bypasses locks placed by other items and means you can get dirty data in your results in the process.
June 11, 2003 at 9:28 pm
If you're worried about conflicting locks try changing the value for LOCK_TIMEOUT system var. If your procs are not involved in data modification and data being read is small,
all shared locks are released as soon as the data is read. Therefore any transaction
that needs to modify data can update its lock to exclusive without causing any confilict.
This might not be ture always so I recommend setting the lock_timeout system var. For more info. on this refer to Lock_Timeout on books online
MW
MW
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply