Bizarro locking/memory issues

[Winkie]

set up statspack, set up snaps for every 5 minutes and this should tell you what querys are using up the most resources.

This is pretty much what i'm doing at the moment, just reading up on requirements / methods first

That process you showed has someone logging in over the network, you could do a netstat to see who owns that process and where the connection is coming from.

That's a pretty good idea, we use a somewhat centralised query system though so it wouldn't work perfectly

Any login triggers at all that you know of that are doing stupid things?

None at all, i'm convinced this is related to statistics gathering on data in the database but according to the guy who wrote it, that runs infrequently and caches everything.

Statspack seems the right direction to head in for now.