Multiuser local network tweeking access sspeeds

[bkdobs]

I have a data set in a backend database that will be used by multiple users across a 100Mb Intranet ... I am wondering if there would be any speed gains if I used multiple back end data sets as opposed to one big one? Understanding the OS has to manage open file buffers as well ... just thinking that one large file might be more of a resource hog for disk swapping then a number of small files?

Also is there any benifit to locating the front end (code only) part of the database on the local user PC and just linking to the shared data accross the network as opposed to locating both the FE and BE mdb files on the shared network drives?

 

[alvechurchdata]

I am wondering if there would be any speed gains if I used multiple back end data sets

I suppose you might see an improvement if you could put all the finance data into a separate mdb and only link it in when a user requests a finance function.

Also is there any benefit to locating the front end (code only) part of the database on the local user PC

There's a theoretical boost to performance because the local user will be able to open the front end without the delay of transferring it across the net. On the other hand, it's so very much easier to manage a single FE on the server.

Just a word of warning. The users won't notice any change unless you can give them at least a fivefold improvement in speed. Even then they won't actively notice it or thank you unless they've already been complaining about slow response.

Geoff Franklin

http://www.alvechurchdata.co.uk