RE: OPPORTUNISTIC LOCKING, SIDE EFFECTS ON A FILE SERVER.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Opportunistic Locking is really just a performance related thing. It doesn't
matter whether two or seven of your users have a file open, the file will be
shared normally. Only when one single user has a file open will anything
change, and that is usually just that the file information will be cached on
the local PC - hence the need for a lock. But fear not, for as soon as
another user accesses the file, normal locking is resumed. In other words -
don't worry about it, the database may well corrupt with oplocks turned on,
so just turn them off and you probably won't see any difference at all!

"Peter Stackhouse" wrote:

> My Company uses ACT! 6.0 for a contact database. On the ACT! website it is
> telling me to disable OPPORTUNISTIC LOCKING on the server runing ACT! and all
> of the Workstation accessing the ACT! Database on the Server. The ACT!
> Software and the database resides on our 'file server' in which all of our
> companies files are kept, read, and written to on a daily basis. We only have
> 7 people in our company so the chance of more then one person accessing the
> same file at the same time is slim but has happen in the past. What are the
> effects of disabling OPPORTUNISTIC LOCKING on an everyday file server/client?
> Thank you for any assistance you can provide, I don't want to make any crazy
> changes to the server un tell I know what i am doing.
>
> By The way the server is a DELL 2.8 Gig with 512 RAM running MS Server 2000
> Standard.
>
> --
> PAS
>
> --
> PAS
.

Relevant Pages

  • Re: ACT .dbf files not syncronized
    ... It sounds like sync is choking on database files. ... If all users should be sharing one database that database should be on the server and each user's ACT should look there for the database. ...
    (microsoft.public.windows.server.sbs)
  • turn off opportunistic locking?
    ... I was told by an ACT! ... that I MUST disable opportunistic locking or ACT! ... I currently only have one user using the act database at any one time ... the same server where ACT! ...
    (microsoft.public.win2000.file_system)
  • OPPORTUNISTIC LOCKING, EFFECT OF DISABELING
    ... My Company uses ACT! ... Database on the Server. ... Software and the database resides on our 'file server' in which all of our ...
    (microsoft.public.win32.programmer.networks)
  • OPPORTUNISTIC LOCKING, SIDE EFFECTS ON A FILE SERVER.
    ... My Company uses ACT! ... Database on the Server. ... Software and the database resides on our 'file server' in which all of our ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: 2003 server sbs and ACT!
    ... I installed ACT on each client. ... act to that shared database and it is working fine. ... I tried installing it on the server, ...
    (microsoft.public.windows.server.sbs)