"dirty read" ODBC connection

Posted in 2004

Topics: Connectivity: ODBC / JDBC / .NET, Transactions, Locking & Isolation

Anthony Stables — Wed, 16 Jun 2004 08:41:42 — source: IIUG Forums & Mailing Lists

Hello all We have recently moved to IDS9 on Windows 2003 server and it seems to be working fine :-) However, we have several people who connect to the database using Microsoft Access and they are having problems. We have figured out that it is due to locking. I am aware of the SET ISOLATION TO DIRTY READ; statement which should get us around the issue, but there is no way that I am aware of, to pass this through to the informix server in Microsoft Access. We are also having the same problem with our OLEDB connections through our aspx pages. If anyone knows of a way round this your help is greatly appreciate. Many Thanks Anthony Stables astables@farrer.co.uk

↪ replying to Anthony Stables

ramy@chubb.com — Thu, 17 Jun 2004 14:03:51 — source: IIUG Forums & Mailing Lists

I had this problem with etl to a sql server. We solved it by creating a stored procedure that set isolation to dirty read, and used the stored procedure in the first select statement.

Glossary

isolation level