We do not use access locking on our views. The tables are static, so there is no need to allow "dirty reads". Is there any processing/performance advantage to using an access lock on a view? We do have some very large tables (300+ mill rows) that are hit symultaneously by multiple selects. Does a view need to be an access lock for syncronized scanning?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Locking Views For Access
- Thread starter BillDHS
- Start date
rrrkrishnan
Programmer
You will need an access lock only if there is a possibility that the concerned tables will be updated when queries are in progress.
Multiple selects can run concurrently without access locks.
Multiple selects can run concurrently without access locks.
- Status
Similar threads
