Setting db isolation level on transaction without EJB

Question

          I'm using UserTransaction in the servlet container, to control XA transactions.
          We're not using EJB. How do I set the database isolation level? I'm tempted
          to use java.sql.Connection.setTransactionIsolation(). However, the Sun Javadoc
          for that method says you can't call that after the transaction has started (which
          makes sense). Right now, we're starting the transaction, getting a connection,
          closing the connection, and committing the transaction. I guess that order won't
          work if I want to set the isolation level. Or am I mixing apples and oranges
          here? If I use UserTransaction, is it even appropriate to try to set the isolation
          level on the connection?
          All I really want to do is change the default isolation level. We do not need
          different isolation levels for different use cases. (Not yet, anyway.) We might
          have transactions against two different database instances or other resource managers.
          That's why I want to use UserTransaction and XA transactions.
          Thanks!
          Steve Molitor
          [email protected]
          

Answer 1

Only committed transactions are replicated to the subscriber.  But it is possible for the report to see dirty data if running in READ UNCOMMITTED or NOLOCK.  You should run your reports in READ COMMITTED or SNAPSHOT isolation , and your replication
subscriber should be configured with READ COMMITTED SNAPSHOT ISLOATION eg
alter database MySubscriber set allow_snapshot_isolation on;
alter database MySubscriber set read_committed_snapshot on;
as recommended here
Enhance General Replication Performance.
David
David http://blogs.msdn.com/b/dbrowne/