Subject | Re: [firebird-support] Classic to Super Server |
---|---|
Author | Mitch Peek |
Post date | 2008-09-12T14:19Z |
Steve Harp wrote:
don't have similar regrets.
I do have a question regarding shutting down firebird. It seems that
doing a database shut down (forced even) will prevent new processes from
spawning/connecting, it does nothing to those that are still running.
in fact, they continue to be able to access the database.
Neither does shutting down the firebird service remove those running
processes. However, they are no longer functional with regards to
accessing the data.
Is there a protocol for shutting down classic (perhaps to obtain
exclusive access, for metadata changes, etc.?
Thanks,
Mitch
> Hi All,i am switching to Classic today 1.5.x. New box, quad core. Hope I
>
>
>
> I've recently found out that our previous system admin installed classic
> server instead of super server. Our performance with respect to server
> connections leaves much to be desired and I'm assuming that the classic vs.
> super could have something to do with it.
>
>
>
don't have similar regrets.
I do have a question regarding shutting down firebird. It seems that
doing a database shut down (forced even) will prevent new processes from
spawning/connecting, it does nothing to those that are still running.
in fact, they continue to be able to access the database.
Neither does shutting down the firebird service remove those running
processes. However, they are no longer functional with regards to
accessing the data.
Is there a protocol for shutting down classic (perhaps to obtain
exclusive access, for metadata changes, etc.?
Thanks,
Mitch