Re: Undocummented: SET ISOLATION TO DIRTY READ

Andy Kent (akent@cix.compulink.co.uk) wrote: : > Mening that it will even read a row that has been locked in : > exclusive mode? (Note, not a table locked in exclusive mode, just : > one or more rows locked in exclusive mode.) : With DIRTY READ in force, no locks are respected, exclusive or otherwise, : row or table. But remember this only applies to when you're reading : things and (more importantly) it may not be what you really want to do. : Process isolation exists for very good reasons. As Andy says, you must be sure what you are trying to do. If you have a scroll list where you will display a customer # and name (fairly stable data), you may wish to use dirty read to build the scroll list. However, in order to get the freshest data (perhaps for an update process), you would change your isolation level to committed read or better. -- @ David Tomlinson @ @ dtomlnsn@netcom.com @ @ "I want my own monster! Get me a monster now!" @