Re: READ_UNCOMMITTED problem with SQL 2000 and i-net Opta 2000 JDBC "neo" <second714@hotmail.com> wrote in message
news:155f8e7d.0311171747.939d534@posting.google.co m...
> Hi,
> I have a problem to set a JDBC connection as READ UNCOMMITED.
>
> setTransactionIsolation(Connection.TRANSACTION_REA D_UNCOMMITTED)
>
> This is causing lots of blocking on tables
> and update or insert doesn't work properly.
When compared with READ COMMITTED, did you get more or same or less blocking
using READ UNCOMMITTED? Maybe your updates and inserts by themselves
already generate a lot of blocking, irrespective of your reads. This can
happen say for example if you run low on memory and SQL Server starts
locking pages instead of rows.
Another suggestion I can think of is update your JDBC driver to the latest
version.
HTH,
Dave
>
> Does anyone have any idea what I'm missing here?
>
> I asked i-net support and they suggested to call
> setAutoCommit(false) after the above function
> and it didn't work.
> also suggested impltrans = true, and I changed that option on SQL
> and it caused more blocking.
>
> Thanks in advance for any info. |