thisllub wrote:

> The database in question handles connections from a variety of sources
> from sql queries run by ISQL from bash scripts to PHP on web /
> intranet servers and legacy Windows apps like MS Access & Visual basic
> programs.
>
> I suspect it is the interaction with MS Access that causes the most
> problems.
>
> However the problem is real.
> The classic server works without obvious slowdown all the way up to
> its ~ 60 user peak. Once past about a dozen users the superServer
> starts to stall.
>
> I can't attempt to diagnose the problem for obvious reasons.
>

I understand your point, but it remembers me a old saying we have here
in Brazil.
"If you find your wife messing around another man on your sofa, just
shoot the sofa to solve the problem"

The fact CS behaves better than SS for your situation does not implies
it's so superior that you cannot understand why SS exists, the problem
at *your* client code makes SS performs worst than CS as far as I can see...

Without more knowledge about the database state at the time of the
slowdown it is hard to try to help you out.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br