OPPORTUNISTIC LOCKING, SIDE EFFECTS ON A FILE SERVER.

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

Vince
Wed Jul 13 12:42:03 CDT 2005

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

Kevin
Wed Jul 13 21:43:47 CDT 2005

Disabling Opp. Locking has been addressed in the past with SBS, and is
sometimes required, but does not really affect the server otherwise.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q812937

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Peter Stackhouse" <thedual5s@hotmail.com> wrote in message
news:EC4AAF01-3314-4A45-B106-9D0E9F9A6976@microsoft.com...
> 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