--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> Confused...somewhere...

Sorry. Trying to vent but keep it short I did not give you the whole
information. I understand that installations have to be done for each
Classic and SS. We have been using SS quite successfully for a while.

What I was trying to do is to test Classic. So, I uninstalled my SS
and tried some tests with Classic. Then, I wanted to go back to SS
and did a complete uninstall of Classic and reinstalled SS (from the
downloaded Win installation kit).

I could not see my local databases in SS using any of the tools (like
IBExpert) that I could use before. I tried the clean install and
reboot several times with no joy.

I am glad I tried it here first before I tried it at a customer's test
site. Maybe I can learn why now SS does not work so, if I have to
change a customer install from Classic to SS, I don't experience the
same problems. From what I understand, we can change from one server
to another without changing the programs, just settings in the conf file.

Why I am having the problem that the SS does not serve me locally as
it used to?

I have been using your book to set the page sizes and caches on the
production installations. Thanks!

> And those are just some of the "gotchas" that I can think of, while

sitting here in my pyjamas with the day's first coffee, on a rainy

>Saturday morning....

Well, since you are up, in theory, how many concurrent connections can
you expect to have on a machine with 3.2 Gig of RAM (and 8 processors)
using Classic Server? We are having affinity set to one processor
and, as the number of users grows, we have some comments on speed. I
understand that SS can have more pages (we have it at 10,000 of 8 MB
pages) and Classic has other requirements. In theory, reducing the
page count per user and the sort buffer size to an acceptable limit,
how many concurrent connections can we expect to handle?

Thanks, boss.

-Eduardo