Is Access Bringing my System to a halt?

S

Simon

Hi,

I am using Access, (ODBC Dll 4.00.6200.00), to log the progress of a
smallish network, (11 machines).

To give a very basic background, we have 10 client all sending and receiving
messages to/from our 'main' computer.
The 'main' computer logs certain actions on an access table from time to
time but not always.

We only have one table, (LOG), and we have around 30000 rows in it, (around
13Mb), the table is not optimized, no index or anything. We use
CDaoDatabase, (Microsoft Jet (.MDB) database) to access the data.

Now, from time to time, (once or twice a day), the server comes to a
standstill and after some time, (an hour at the most), the server appears to
be back to 100%.
At first we assumed it was a software error or that the network was failing
somewhere down the line.

But we now think that Access is doing something every so often that might
take most/all the CPU usage.

So the question is fairly simple, (I hope), given the situation above, is it
possible that Access be the culprit? Could it use 100% of the CPU?
If so, is there a way of either preventing it and/or logging such events so
we can tell for certain that there is something wrong.

I realize that our table design is flawed and I will look into it. But I
first need to know if Access is bringing my network down or if I must look
in another direction.

Many thanks in advance.

Simon
 
S

Simon

It is hard to say from here. Since Access can be programmed to do so
many things in so many different ways, it may be doing something. It is
more likely that you are experiencing problems due to poor database
design, lack of split (front end - back end) design or a improperly
configured LAN.
Click to expand...

I didn't do the LAN install, but the company that did it assured us that it
is configured properly, (they would say that wouldn't they).
And if there was a problem with the network, (like storms or collisions),
then the network would always be slow, not on a daily basis for a finite
amount of time.

As I said, I agree that the design is poor, but would that really explain
Access going into overdrive for 'x' amount of time on a daily basis?
I mean, what could Access be doing on 25000 records?

In fact I am not even certain that Access is the problem, but I am looking
for a way to say without a doubt if it is.

Simon
 
T

Tony Toews

Simon said:
We only have one table, (LOG), and we have around 30000 rows in it, (around
13Mb), the table is not optimized, no index or anything. We use
CDaoDatabase, (Microsoft Jet (.MDB) database) to access the data.

Now, from time to time, (once or twice a day), the server comes to a
standstill and after some time, (an hour at the most), the server appears to
be back to 100%.
At first we assumed it was a software error or that the network was failing
somewhere down the line.

But we now think that Access is doing something every so often that might
take most/all the CPU usage.

So the question is fairly simple, (I hope), given the situation above, is it
possible that Access be the culprit? Could it use 100% of the CPU?
If so, is there a way of either preventing it and/or logging such events so
we can tell for certain that there is something wrong.

I realize that our table design is flawed and I will look into it. But I
first need to know if Access is bringing my network down or if I must look
in another direction.
Click to expand...

Unless there is some wield code running on a client system I can't see
Access by itself slowing down the server.

When you run Task Mgr on the server is their any particular process
which is consuming CPU? What about the network traffic pane?

When you look at the flashing lights on the network switch is there
any one particular system which is very active during this slowdown?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top