M
MBursill
I’m having a problem with Access not using all the available
bandwidth, and transferring upwards of 8x the full database size for a
simple operation. The problem is fully reproducible using the
Northwind database.
First, our company has a database which since upgrading to A2007 has
been showing very poor performance. It runs fine when the linked
database is local. All systems are XP, and I have tried the program on
our 2003 servers as well as on a smaller test LAN made up of three XP
systems.
Refreshing the links to the database from a test client, I found it
using 2-5% of a 100Mbps link, and taking about 2-3 minutes.
Through a lot of trial and error I’ve determined that refreshing the
links is slow once any single client has a lock on the file.
I wasn’t so sure the problem was limited to just our database. I fired
up Northwind, saved a copy of the DB to a share folder. On two
different clients, I created new accdb files linking to the same
Northwind backend. If I open the orders table on one client to
establish a lock (this can be seen by the creation of the laccdb file)
and then use the second client to relink the Northwind database, it
takes about two full minutes to do the refreshing. It’s only using
about 2-5% of the network and is pulling about 24MB. That’s incredible
considering the full database is only 3MB!
Things I have tried:
- Turning off OpLocks
- Toff file caching
- Disabling virus scanning
- Disable SharingViolationDelay and SharingViolationRetries
- Different combinations of hardware (systems, switches, cables, etc.)
Is this normal? If it’s normal, why?
Thanks.
bandwidth, and transferring upwards of 8x the full database size for a
simple operation. The problem is fully reproducible using the
Northwind database.
First, our company has a database which since upgrading to A2007 has
been showing very poor performance. It runs fine when the linked
database is local. All systems are XP, and I have tried the program on
our 2003 servers as well as on a smaller test LAN made up of three XP
systems.
Refreshing the links to the database from a test client, I found it
using 2-5% of a 100Mbps link, and taking about 2-3 minutes.
Through a lot of trial and error I’ve determined that refreshing the
links is slow once any single client has a lock on the file.
I wasn’t so sure the problem was limited to just our database. I fired
up Northwind, saved a copy of the DB to a share folder. On two
different clients, I created new accdb files linking to the same
Northwind backend. If I open the orders table on one client to
establish a lock (this can be seen by the creation of the laccdb file)
and then use the second client to relink the Northwind database, it
takes about two full minutes to do the refreshing. It’s only using
about 2-5% of the network and is pulling about 24MB. That’s incredible
considering the full database is only 3MB!
Things I have tried:
- Turning off OpLocks
- Toff file caching
- Disabling virus scanning
- Disable SharingViolationDelay and SharingViolationRetries
- Different combinations of hardware (systems, switches, cables, etc.)
Is this normal? If it’s normal, why?
Thanks.