Disabling Opportunistic Locking (oplocks)

  • Thread starter Thread starter Roger
  • Start date Start date
R

Roger

To avoid corruption and performance issues with a
customized Access database the developer has advised that
we disable this registry setting on our file server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanman
Server\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (Enabled by Default)

We have other Access databases on our server. Is there
any downside or security issue to doing this?
 
Shouldn't be. Been there did this some years back. Best solution is to
migrate the Access backends to SQL server and be done with it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| To avoid corruption and performance issues with a
| customized Access database the developer has advised that
| we disable this registry setting on our file server:
|
| HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanman
| Server\Parameters
| EnableOplocks REG_DWORD 0 or 1
| Default: 1 (Enabled by Default)
|
| We have other Access databases on our server. Is there
| any downside or security issue to doing this?
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top