V. Poor Performance with MS Access

From: Alex (alex_at_mailinator.com)
Date: 05/26/04 

Date: Wed, 26 May 2004 05:27:46 -0700

By chance I have observed something that may help us
colectively solve this problem. Until last week I have
been running an Access 97 based management system with up
to 40 clients accessing up to 8 separate back-end
datasources from up to 5 segmented FE's on a Novell
Network. It's been working brilliantly for about 3 years.
I then moved the data sources onto our BRAND NEW - UNUSED
Win 2000 server and experiences a 10% errosion of
performance (anecdotal), which I expeced. This performance
was acceptable. Over the following 4 days however,
performance steadily fell-off to the point where I had to
move back to Novell. Posting records or updating server
side data was taking 30 seconds where we had been
experiencing 1 - 2 seconds - form opening was dreadfully
slow. In the past I have moved Access systems onto
established Win 2000 platforms, and experiences dreadful
performance from the start. On this occasion - as I have
said I started off on a new unused server and performance
started off just fine before deteriorating steadily to the
low levels I had experienced before. What could Win 2000
be doing that would build up to a performance problem.
Logs? User access rights? Buggeration factors? Can anybody
shed any light?
Thanks guys
Ben

Relevant Pages

  • V Poor Performance with MS Access
    ... been running an Access 97 based management system with up ... performance steadily fell-off to the point where I had to ... Posting records or updating server ... established Win 2000 platforms, and experiences dreadful ...
    (microsoft.public.win2000.advanced_server)
  • Re: WINS frustration
    ... your experiences won't be different. ... And yes a single master. ... DC3 and DC4 are 2003 server machines. ... trusted domain with two WINS servers as well (TRUST1 and TRUST2). ...
    (microsoft.public.windows.server.active_directory)
  • freezing, hard locking, and debug.mpsafenet=0
    ... In my experiences this usually resulted in bad memory but after swapping out the memory for new memory the issue still persisted. ... As time went on I eventually pulled the hard drives out of the server and put them into another server with completely different hardware. ...
    (freebsd-questions)
  • freezing, hard locking, and debug.mpsafenet=0
    ... In my experiences this usually resulted in bad memory but after swapping out the memory for new memory the issue still persisted. ... As time went on I eventually pulled the hard drives out of the server and put them into another server with completely different hardware. ...
    (freebsd-questions)
  • Re: Disk Configuration Best Practices
    ... I have 5 drives in the SQL server ... > much data will be read & written etc. Ideally you want the OS, SQL ... >> configuration for a new SQL server. ... and our management system vendor's default ...
    (microsoft.public.sqlserver.setup)
Loading