Moin!

I know that CS Win is in a 'somewhat experimental state', but I am
nevertheless using it to my full satisfaction in our company, and it
is for most tests that I have been running indeed faster than the SS
variant.

One problem I have is with 'zombie' processes. And I can not find the
FINAL solution to this. The installation package for CS Win installs
with "GuardianOption = 1" and this results in processes not being
ended after detaching a client.
If you set "GuardianOption = 0", after a restart of the server
everything FIRST works fine. I can test with 4 or 5 clients, each of
them opening 4 databases. Whenever a client detaches, the number of
processes lowers by 4 on the server. As soon as nobody is attached
anymore, there is only 1 (the standard) process left running on the
server.

But... after some time (can be a usual working day) the server again
is in a state where processes are not terminated when the client is
detached.

With my limited knowledge of the server system (Win2003) I do not have
any idea how to trap down the reason for those 'zombie' processes.

Does somebody out there have an idea where to look and what to try?
Killer queries or overly long transactions are not a matter. I checked
that OIT is following the OAT (difference: 1) and the OAT again is
only 1 lower then the "Next transaction".

Thanks for any ideas,
André