Re: IsolationLevel workaround?
- From: "Bob Barrows" <reb01501@xxxxxxxxxxxxxxx>
- Date: Thu, 2 Apr 2009 15:39:37 -0400
David Rueter wrote:
I would like to use the SQL 2005 SNAPSHOT isolation level. IAccording to BOL, the SQL Native Client provider should provide this
understand that the ADO IsolationLevelEnum has not been updated for
SQL 2005.
I thought it would be OK if I left the connection set to
cn.IsolationLevel=adXactReadCommitted, and then I issued a statement
on the connection like:
cn.Execute('SET TRANSACTION ISOLATION LEVEL SNAPSHOT');
However, ADO is kind enough to set the isolation method back to
ReadCommitted whenever I begin a transaction. And, I am not allowed
to change the isolation level to SNAPSHOT inside a transaction if the
isolation level was not SNAPSHOT at when the transaction was started.
Argh...
So I thought if I set cn.IsolationLevel=adXactUnspecified, then
issued the Execute statement as above to set the isolation level for
the connection that I would be OK. However, then I get errors like:
"Neither the isolation level nor a strengthening of it is supported."
Is there any way to get ADO to use the SNAPSHOT isolation level? Or,
is there at least any way to get ADO to NOT set the isolation level
at the start of a transaction so that I can set the isolation level
myself?
support. I haven't tried it myself, but are you using SQLODEDB or
SQLNACLI for your provider?
See the topic "Working with Snapshot Isolation"
--
HTH,
Bob Barrows
.
- Follow-Ups:
- Re: IsolationLevel workaround?
- From: David Rueter
- Re: IsolationLevel workaround?
- References:
- IsolationLevel workaround?
- From: David Rueter
- IsolationLevel workaround?
- Prev by Date: IsolationLevel workaround?
- Next by Date: Re: IsolationLevel workaround?
- Previous by thread: IsolationLevel workaround?
- Next by thread: Re: IsolationLevel workaround?
- Index(es):
Relevant Pages
|
