Shared MS Access 97 database causing 100% CPU usage on client workstation.
Posted on 2004-11-24
We have an MS Access 97 databse stored on a network server that is shared by 30 to 40 users. The server hosting the db and the client switch both have a GigE connection to the Cisco core switch. The switches are optimized, spanning tree is correctly configured, portfast is enabled on the workstation ports and not on the uplinks, etc. Optimal network configuration, and everything is extremely fast.
The domain is Windows NT 4.0 based. The server hosting the db is Win2k Adv. Server, Compaq Proliant, dual PIII 1Ghz Xeons with 4 GB RAM. The client workstations are both WinXP and WinNT, P3 and P4, from 64 mb of RAM to 368 mb of RAM, running both Office 2000 and MS Access 97. The db is accessed through a proprietary C+ app developed within our organization (it's garbage), and is only compatible with Access 97. Users access the db through a mapped drive created at logon, and the script calls the server by ip address, not the netbios name.
Using MS Access 97 itself causes no issues, and accessing a db on the network works without any issues. When this application opens this 100mb Access 97 database, the CPU goes straight to 100%. After you login to the application to use the database, the CPU remains at 100% for close to 3 or 4 minutes before returning to normal. At this point, simply clicking the mouse on an empty part of the application window will send the cpu back to 100% for 30 or 40 seconds.
We will be migrating to AD in the next 6 months, so please, no suggestions regarding our archaic infrastructure. We have no control over those aspects of this scenario, as it is dictated by others who know nothing technical.
1. Could this be a version compatability issue of either MDAC or MS Jet?
2. Could this have anything to do with the fact that Access 2000 and Access 97 are both installed on the workstation (in seperate directories)?
3. Is there a Windows XP (SP1) service that if it were disabled, would have a negative impact on the accessing of a shared database in these conditions? Same question for Windows NT Workstation.
4. Is there a Win2k Adv. Server service or process that could help or hinder this?
I understand that there are lot more variables in play here, but they would take forever to list. But I will provide more info if requested. The app developer is convinced that this is a network problem, when it is clearly not. Any help is much appreciated.