[AccessD] Speeding up the database

Hi Jim et all

The issue with Opportunistic Locking on Windows servers has been
touched several times. 
I located this tool which does the "dirty" work:

  http://www.resumate.com/windows_xp2000nt.htm

</quote>

To simplify the process of disabling Opportunistic Locking, you can
download and run the following utility: 

set_oplocks.exe

Please note that this only needs to be done on a Windows XP/2000/NT
machine acting as the file server. This includes peer-to-peer network
environments as well as dedicated server environments.

</quote>

/gustav


> A couple of other performance points:

> 1. Make sure that the MDB's are nto being virus scanned when opened.
> 2. Turn off opportunistic locking on the server.
> 3. Make sure that all clients and server(s) are running the same default
> network protocol.
> 4. Hold open a reference to the BE's as soon as the app starts and don't
> close it until the app closes.  This is the #1 item that you need to do.

> 5. Over indexing can be just as bad as under indexing.  Use the SHOWPLAN
> function to see what JET is actually doing when it runs a query.  It's
> possible that it's not even using indexes that you setup.

> 6. Use ISAMSTATS() to determine if any JET engine setting changes would
> help.

> The last two can take some time, but often pay off.

> Jim Dettman
> President,
> Online Computer Services of WNY, Inc.
> (315) 699-3443
> jimdettman at earthlink.net