Hello,

I have a C/S software that is workin fine by a lot of users with
clients and servers and also at single machines...

Now I have one customer who installed the software at a single pc (P4
2,6, 1G RAM,.. XP (don't know the release))

Whenever the server starts triggers the software becomes extremly slow..
Some storing operations that take about 1 - 1.5 sec at all other
customers (real C/S <1sec.) take up to more than 60 sec. (?) step by
step in a progress bar...

The customer had installed Antivir. So I asked him to disable all virus
software for testing.... he did this.

software + server are installed at drive d:. There is no ini file for
server. So all temp files are created at drive c:.. (think so..)

Nearly all stuff that is executed works fine. But when the server
starts a lot of trigger operations execution time is going from 1 to
mor than 60 sec.

I have never seen that before... I have a testing system (P2 400Mhz..,
W2K that needs about 2-3 sec. for the same operations....

I really have no idea where to look (ask the customer) what to do...

Maybe anyone has seen something like this or can give any hint where to
look....

TIA
ralf

Does the client have enough RAM to run both the server and the client?
Also why is he running C/S on his client?  It would make more sense to
run in local mode if the data is also on the client.  In our app a
client can choose local or remote connection at startup. Your triggers
should also be part of your client application.

Ralf,

<< Whenever the server starts triggers the software becomes extremly slow..
Some storing operations that take about 1 - 1.5 sec at all other customers
(real C/S <1sec.) take up to more than 60 sec. (?) step by step in a
progress bar... >>

Do normal operations on a table that are outside of a trigger slow down also
?  It sounds like either AV software or something external affecting the
performance.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Ralf,
> Do normal operations on a table that are outside of a trigger slow
> down also ?  It sounds like either AV software or something external
> affecting the performance.

just got the info that there is a RAID system in.. (Promise controller)
Seems that the RAID is responsible for the slowdown.
Just a couple of normal operations on tables .. there was no problem.

Whenever triggers (search and replace a couple of tables) are executed
it slows down. I just did a search on this and found similiar behaviour
(slowdown) when synchronizing of a RAID takes too long..

I think that during the trigger operations a lot of temp files are in
use by the dbsrvr... so I'm not sure what's going on in the RAID at
this time. So I will wait until anybody checked the RAID.

regards,
ralf

David,

> Does the client have enough RAM to run both the server and the client?

Yes, there is enough RAM (2 GIG)..

> Also why is he running C/S on his client?  It would make more sense to
> run in local mode if the data is also on the client.  In our app a
> client can choose local or remote connection at startup. Your triggers
> should also be part of your client application.

You are right, but we don't have a lot of single/local install's.
Normally it's always multiple client's with server... that's why I
didn't put the triggers in the app.

regards,
ralf