| Angel Saenz-Badillos[MS] 2006-02-01, 8:23 pm |
| Just trying to understand your scenario, we currently don't allow changing
the default isolation level at the connection level and I really don't see a
good reason for this feature right of the bat.
The one thing that may be interesting is when you want to modify the default
ReadCommitted transaction level to Snapshot, fortunatelly this can be
achieved at the DBMS level by setting READ_COMMITTED_SNAPS
HOT to ON on the
database that your application is using. When this is set all your Read
Committed transactions (Default) will behave as Snaphot transactions.
Hope this helped, if not please expand on the scenario that you are
interested in.
--
Angel Saenz-Badillos [MS] DataWorks
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://weblogs.asp.net/angelsb/
"pjhavariotis" < pjhavariotis@discuss
ions.microsoft.com> wrote in message
news:4A1C375B-0262-46D0-971F- D3FD1FE31C27@microso
ft.com...
>I am using the newly released JDBC driver (SQL Server 2005 JDBC Driver)
>with
> WebSphere Application Server 5.1.1.
> Is it possible to setup the isolation level for ALL the connections of the
> pool in the connection properties of the datasource?
>
> Thanks for your help.
|