Speeding up Processing from Server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A process is run on my work computer with Access 2000 which reads data from a
server. At home I run a similar process but it uses Access 2003 and the data
is read from the Jet database. It runs in a fraction of the time.

Is anyone aware of how the same program could run with such a drastic time
difference. Are Access 2000 and 2003 that much different ? Is it because
data read from a server is that much slower ? Are there Access system
parameters or Windows parameters which must be changed ? Is it possible the
work computer is just slower or needs defragging ? What are the general
causes of slower processing speed assuming the computer hardware on both
computers is basically the same ?
 
What is the back-end (server end), another Access file? If so, yes, reading
across the network is slower. Yes, it is possible that the work computer is
slower. If the processors are about the same on both computers (home and
work) then other processes running on the computer and amount of available
RAM will make a difference. I don't know of much difference between Access
2000 and 2003 in performance.

There are some things you can do to improve performance across the network.
One of the biggest boosts to performance I've seen is keeping a lock on the
back-end file (LDB Locking). For how to do this and other tips on network
performance, see this link.

http://www.granite.ab.ca/access/performancefaq.htm
 
If the Jet DB is on your PC or laptop, the performance will always be
faster as there is no network traffic to contend with. Keep in mind that
when you're dealing with anything coming across a network, it isn't just
you're data that's there. At any point in time, there would be countless
emails, files, HTTP requests, and other data being sent on the network,
not to mention any overhead from having to send the request over a
network to begin with. If your organization pretty much shuts down
overnight, go in at 2AM and run the process, you should find that it
runs much faster than at 2PM. Also, keep in mind that the processor
speed of the PC's can make a difference as well.
 
Thank you.

Wayne Morgan said:
What is the back-end (server end), another Access file? If so, yes, reading
across the network is slower. Yes, it is possible that the work computer is
slower. If the processors are about the same on both computers (home and
work) then other processes running on the computer and amount of available
RAM will make a difference. I don't know of much difference between Access
2000 and 2003 in performance.

There are some things you can do to improve performance across the network.
One of the biggest boosts to performance I've seen is keeping a lock on the
back-end file (LDB Locking). For how to do this and other tips on network
performance, see this link.

http://www.granite.ab.ca/access/performancefaq.htm
 
Thank you.

David C. Holley said:
If the Jet DB is on your PC or laptop, the performance will always be
faster as there is no network traffic to contend with. Keep in mind that
when you're dealing with anything coming across a network, it isn't just
you're data that's there. At any point in time, there would be countless
emails, files, HTTP requests, and other data being sent on the network,
not to mention any overhead from having to send the request over a
network to begin with. If your organization pretty much shuts down
overnight, go in at 2AM and run the process, you should find that it
runs much faster than at 2PM. Also, keep in mind that the processor
speed of the PC's can make a difference as well.
 
Back
Top