Jos,

Typically no....

There are a few tricks however. If the tables are really used readonly, you might want to make them readonly. It will enable the OS to buffer them on the workstation.

when using a database container, it might be a good idea to make the database readonly. It will surely speed up things as then everytime a table is opened, the database info will come from the local cache rather than the network.

There are other factors involved as well. By default Windows allows for optimistic oplocking which means that the workstation is able to cache data from any file as long no data is written to the table by other workstations (search the kb for opportunisitc locking).

Another tip is to use a free tool, filemon (www.sysinternals.com). This tool will enable you to track down network bottlenecks in your application. It will give you some understanding how tables are openened, records and indexes are used in your application. Personally I've been using this tool for many years to track down performance problems.

HTH,

Walter,





>Hi All
>
>Would the use of the NOUPDATE clause further speed up access to shared tables on a network server that do not require data to be written to them but only read from them?
>
>Thanks