Thanks Maya - I appreciate the feedback.



Could you elaborate on the quotes around "things" that you didn't with SS?



Sorry - I got this one wrong: "can't perform backup/restore over the
network". Looks like 1.5.1 and up has full services manager.

This is where I got the comparisons:
http://www.firebirdsql.org/manual/qsg15-classic-or-super.html



Should the "older technology" be a concern of mine?



Thanks again,

Kevin









From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Maya Opperman
Sent: Monday, June 20, 2011 10:43 PM
To: 'firebird-support@yahoogroups.com'
Subject: RE: [firebird-support] Classic Server

>>recollection is that Classic processes do not influence each other so if

one

>>of the ugly reports is run, the other users won't be affected.

Correct

>>I have to stay with FB 32-bit for now until I
>>can replace the few FreeUDFLib functions used in the database. I may try

to

>>do this before they bring up the new server so I can use FB 64-bit.

I was in the same boat. Managed to find replacements for all the FreeUDFLib
functions I was using with Fb 2.1.

>>And with Classic you can't perform
>>backup/restore programmatically over the network, you have to be local on
>>the server.

Why do you say that, I do backups and restores over the network all the time
with classic

I did find that with Fb 1.5 with classic I needed to put quotes around
things that I mustn't with superserver, but with FB 2.1 I no longer need to
do that.

>> It looks like Classic can handle multiple CPUs better than Superserver

Yup, that's why its popularity returned, even though the technology is
older.

>>and events can't be used if the server is behind a firewall or
>>secure tunnel. (everyone is on the same side of the firewall in this case)

AFAIK, this is the same whether you're using CS or SS, but I haven't done
much more than just play around with events a bit

>>It would be nice hear of anyone with experience between moving between the
>>two architectures and if there is anything else I need to be aware of.

I used the 2 interchangeably for several years.

If you created your database with the superserver default page size of 3000,
then you should change it to the classic recommendation (between 75 and 150)
especially if you have lots of users, else it will use too much memory, and
slow things down during busy periods.

Your Delphi component set should have a database properties component which
will help you view and change that setting easily.

One other thing I have found, is that developing on classic is a little more
difficult. We use IBExpert to modify stored procedures for a lot of our
reporting, and classic server is a lot more sensitive to procedures being in
use when you try modifying them. You get an error "Object is in use" and you
have to go check all your connections, and make sure they're all
disconnected, before you can make the change. (sometimes Delphi connects at
design time, so don't forget to check that one too)

Cheers
Maya





[Non-text portions of this message have been removed]