Opportunistic Locking Need more info

Hello all first post here. I am doing some research in the issues of Opportunistic Locking and Windows XP I have searched these articles and looking for some more information. can you all help me?

Docs found
Q826852
Q300083
Q217351
Q296264
Q329170
Q303528
Q300216
Q810907
they are not all on Oplocks however they are related in some way
if you know of any other information on Opportunistic Locking and Windows 2000 Server and Windows XP please post

Thank you in advance

Regards Gentooer

 

http://www.jsiinc.com/SUBG/TIP3100/rh3108.htm

http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

 

Are you just doing general research on an interesting technology, or do you have a specific objective (programming or a problem) you are trying to solve?

 

I was asked to investigate this issue for work due to database corruption on an access database over a network with a Windows XP environment

 

Well, the quick test is just to turn them off on the server and see if your incidents of corruption decrease. If they dont, then you have lots of avenues to pursue. If they go down, then you can just run with them off.

There tons of stuff that will corrupt MDBs. Anything from bad network connectivity, to excessive locking (ie: too many users), or leaving unused connections open. Often disabling oplocks will mask the scenario causing the corruption.. Seen a lot of people just take that as the solution, but usually its not the true cause. Lots of access FAQs out there in google that have best practices, and common causes documented. Depending on your scenario, it might be better to go down those rat holes before you take a 10% perf hit. *Shrug*

 

Thanks a lot. I know I found a lot of stuff However different customers have different setups. pretty much I need to setup a network environment with different O/S and just test it with a whole bunch of configs to get an accurate test result. using 10MBS card network to 1000 networks will just have to see thatnks for your help