Hi all,
I'm using Hibernate 3.01. We are migrating to SQL Server 2005 and would like to use the SNAPSHOT isolation level.
Using hibernate.connection.isolation and hibernate.connection.url, it works great (tested with DataDirect and jTDS drivers - head revision as per 15.06.07)
However, if I use hibernate.connection.isolation and hibernate.connection.datasource, the isolation level is ignored.
I use Weblogic 8.1 sp6 connection pools.
Have you experienced this behaviour ? I am probably missing something here ... Any help more than welcome !
failing hibernate.properties
hibernate.dialect=org.hibernate.dialect.SQLServerDialect
hibernate.connection.datasource=com.sitel.ciclop.db.opRecettage
hibernate.max_fetch_depth=0
hibernate.cache.provider_class=org.hibernate.cache.EhCacheProvider
hibernate.show_sql=false
hibernate.connection.isolation = 8 # serializable - SNAPSHOT for DD Driver
hibernate.max_fetch_depth=0
working hibernate.properties
hibernate.connection.url=jdbc:datadirect:sqlserver://server\\\instance;databaseName=db;snapshotserializable=true
hibernate.connection.username=user
hibernate.connection.password=pwd
hibernate.connection.driver_class=com.ddtek.jdbc.sqlserver.SQLServerDriver
hibernate.dialect=org.hibernate.dialect.SQLServerDialect
hibernate.show_sql=false
hibernate.connection.isolation = 8 # serializable - SNAPSHOT for DD Driver
hibernate.cache.provider_class=org.hibernate.cache.EhCacheProvider
hibernate.max_fetch_depth=0
Kind regards,
Regis
|