Re: Setting isolation level in Ace

Another useful place to look for this sort of information is : www.ibm.com/software/data/support I put in "Isolation Levels", selected solve a problem, and the first artivel returned was : Setting Isolation Levels in Ace and Perform This document explains how to set isolation levels in Ace and Perform. malc_p@btinternet.com (Malc P) wrote in message news:<8c28402a.0403040202.486106d4@posting.google.com>... > andykent.bristol@virgin.net (Andy Kent) wrote in message news:<a3525a11.0403030719.34c9f1f7@posting.google.com>... > > Thanks, that's the one. Any idea what values it takes? > > > > I remember seeing it either in some Release Notes or marketing blurb, > > but I've never seen it in any manual. Unless it's very well hidden. > > > > Andy > > > > > I started to trawl the manuals, but then lost my will to live and > instead did a search on cdi and guess what I found (from our own > Jonathan Leffler, posted 27/10/04 - yup he's *THAT* vintage, folks!) > > > SPERISOL and SACEISOL Environment Variables > =========================================== > > Version 4.11 of INFORMIX-SQL provided the ability to run PERFORM > forms using dirty read isolation with an OnLine backend. In > Version 4.12, this feature has been extended to allow ACE reports > and PERFORM forms to be run in any isolation level. > > This feature will only be of interest to you if you are running > ISQL with OnLine, and is provided mainly to provide compatibility > for those who upgrade from Standard Engine to OnLine. The > following description assumes an understanding of "levels of > isolation" in OnLine databases; you can find this information in > your OnLine Programmer's Manual. > > The Standard Engine always runs in dirty read mode; the default > isolation level for OnLine databases with no logging is dirty > read, for MODE ANSI databases the default is repeatable read, and > for databases with transaction logging the default is committed > read. Each mode has a different tradeoff between isolation and > concurrency. > > When you upgrade from a Standard Engine to OnLine, the isolation > level will automatically change, as described above. Usually, the > new default isolation level is more suitable than the old; > however, in some cases, it will be preferable if the concurrency > level remains the same under OnLine as it was under Standard > Engine. > > This can be accomplished in I4GL by adding 4GL code that sets the > isolation mode to dirty read, and it can be similarly accomplished > in ISQL scripts. > > To set the isolation level for PERFORM, set the environment > variable SPERISOL to one of the following values; similarly, to > set the isolation level for ACE, set the environment variable > SACEISOL to one of these values: > > dirty read > committed read > cursor stability > repeatable read > > *** END cdi archive rip > > (NB export in your chosen shell, quotated, lower case only) > HTH > Malc