Long running transaction

  • Thread starter Thread starter Oscar Thornell
  • Start date Start date
O

Oscar Thornell

Hi,

I have a long running transaction that gets started by calling a stored
procedure using the OpenXML functionality.
While this transaction is running all other reads from the tables used in
the transaction are blocked and results in a timeout.

The isolation level is set to "Read Uncommitted" for the long running
transaction. Why does it still prevent other connections from reading?

Should I turn everything around and start a new transaction(s) for my read
operation(s) and set the isolation level to "Read Uncommitted" thus
explicitly telling my read operation(s) to ignore the lock and just read...

Regards
/Oscar
 
I am not a fan of ReadUncommitted, thats like saying .. "Uhh .. yeah lets
just pretend this is a transaction okay .. but keep it under the covers will
ya".
 
Back
Top