Re: Access Database Application has began running slow on Workstations.

From: Henry Craven [SBS-MVP] (IUnknown_at_Dot.Nyet)
Date: 02/15/05


Date: Tue, 15 Feb 2005 14:13:21 +1100

Unlike SQL Server where you can run Stored Procedures and Triggers on
the Server, the actual processing in MS Access is done on the front end,
so that is where the Processor Load is. The server is just Data Serving.

Depending upon how well (or badly) the app has been written, Access will
fetch only the indexes, process the queries and then fetch the minimal
dataset that results from jet across the wire, Or it may be that it
fetches the Complete Datatable each time.

e.g. I've seen dozens of Customer Dropdown Listbox, that weren't pre
filtered nor limited to the just the Index and Name, and so dragged the
whole customer table across the wire each time instead of just the few
pertinent Names and PKs, and then bringing over the Address and other
related data for just -that- record.

I'd be 98% sure it's a design issue.
( Check the net traffic using Perfmon. - if logging don't forget to turn
it off .)

Disk I/O, Switching and LAN quality will have an effect on the handling
the data throughput so you can tweak that somewhat if you can't get the
Application properly optimised ( p.s. MS Access comes with a
Analyser/Optimiser wizard, and there are basic optimisations like
turning off Autocorrect etc you can apply at the non Code/design level
also.. )

The guys at comp.databases.ms-access can help you with a lot of that.

-- 
Henry Craven {SBS-MVP}
CI Information Technology
----------------------------------------------------
Melbourne SBS Users Group
http://groups.yahoo.com/group/melb-SBSusers/
"Doug B -db-" <dburrows_nospam-@dbnational.com> wrote in message 
news:vWbQd.58058$sr1.43477@fe2.texas.rr.com...
> There is a front-end on the workstations. I pretty sure the slowdown 
> began
> suddenly but at the same time the users say it's degrading as more 
> data it
> added.
>
> I was monitoring the processor usage for a while today and while there 
> was a
> few spikes up around 90% and some moderate usage around 50-60% much of 
> it
> was below that.
>
> I'll be meeting with the client to try and get more specific info 
> about when
> it began in relation to when the users began to use this db.
>
> Thanks so much
> db
>
>
> 


Relevant Pages

  • Re: [PATCH] NFS server does not update mtime on setattr request
    ... to avoid an over the wire call if the size of the file was not going to ... testing again shows the correct semantics. ... The server is already going to have such a check in it ... such as SunOS and older versions of Linux will require this change in order ...
    (Linux-Kernel)
  • Re: Question on Unix FIFOs - why slow when on NFS?
    ... > happens in the NFS client machine's kernel. ... > machine's kernel - not the kernel in the NFS server. ... > Reading the info about the device file happens over the wire. ...
    (comp.unix.solaris)
  • Re: Question on Unix FIFOs - why slow when on NFS?
    ... > happens in the NFS client machine's kernel. ... > machine's kernel - not the kernel in the NFS server. ... > Reading the info about the device file happens over the wire. ...
    (comp.unix.programmer)
  • Re: domains
    ... As long as it is in a separate domain it will not affect your existing ... You can run the two domains on the same wire with little (network ... I just want to boot this test server up on the LAN. ...
    (microsoft.public.win2000.active_directory)
  • Re: SQL Server Service jumps to 100% of CPU time
    ... > Our customer is running our custom application that uses MS SQL Server ... Periodically, maybe once a week or so, the processor usage ...
    (microsoft.public.sqlserver.server)