On Mon, 1 Dec 2003 21:26:10 +0000 (UTC), turbomenda wrote:

> I'm running a quite big (over 1GB) database. There are several programs
> and more than 100 users connected to that DB. My problem is the database
> started to work really, really slow (%
> processor usage maxed out throughout the day)
> This obviously looks like an unoptimized query got through to one of the
> client programs (I am doing a large refactoring of the programs recently)

My guess is that you have a long-running (open) transaction.
Can you post the statistscs (from the header page) when your db is slow?

After you check the statistics, get everyone out of the db and either do a
backup/restore or a sweep. With 100 users this may be 'inconvenient', I
know. If the backup/restore cycle 'fixes' the slowness, you'll have to
check (and, probably, change) your handling of transactions in your app
before the problem will go away permanently.
Yoy may be able to find a lot of previous messages on this list concerning
this problem.

--
Aage J.