Query and Isolation Level

I have a question about any potential benefits from using low isolation
level in simple queries. (Level 1,2)

I have an application with many users. They're all running reports which do
simple queries against the database. All of the queries are pretty much the
same with minor variations.

There is also a great deal of contention in the database.

If I have a query. Is there really any benefit to doing something like.

select a,b,c from table A where A.name = 'FOO'
at isolation level read committed

Please excuse the syntax, I know it's probably not exact.

-Wayne


.

Relevant Pages

  • Re: access 2003
    ... I would focus on the queries behind the combo boxes. ... the Access 97 database, I wouldn't have thought any expressions would be ... When you select a customer and a job in the two combo boxes, ...
    (microsoft.public.access.conversion)
  • Re: access 2003
    ... I would focus on the queries behind the combo boxes. ... the Access 97 database, I wouldn't have thought any expressions would be ... When you select a customer and a job in the two combo boxes, ...
    (microsoft.public.access.conversion)
  • Re: Run action query in back-end from front-end database
    ... whatnot in the back end database. ... The queries are housed in the back end ... The reason I have the upload tables in the back end is that it will be on ... Rick's code uses DAO, and Access 2000 doesn't have a reference set by ...
    (microsoft.public.access.externaldata)
  • Re: User has group permissions to object, but still denied access.
    ... permissions to those query objects. ... The owners for the other 68 queries can be changed. ... may have been some of the original queries created in the database. ... Regarding the security, the database was converted from an Access 97 ...
    (microsoft.public.access.security)
  • Re: access 2003
    ... I removed the parameters from the form query source. ... synchronize combo boxes to the detail section or the parameter form query ... forms queries and the SQL because syntax of the SQL will change randomly. ... the Access 97 database, I wouldn't have thought any expressions would ...
    (microsoft.public.access.conversion)