Subject | local connections to classic server in windows |
---|---|
Author | Dan Wilson |
Post date | 2005-04-03T15:39:09Z |
I decided to try out the classic server, as I understand it's performance can be better than superserver for high-transaction environments with low numbers of connections to the database. I also understand that one can connect to classic server via local connections for even better performance.
I uninstalled FB superserver 1.5.1 and then installed a fresh copy of classic 1.5.2. I can now connect to databases, but only by using "localhost:". gsec is also unable to connect to the security database unless I use the -database=localhost:"c:\Program Files\firebird\firebird_1_5\security.fdb" switch. isql also cannot connect to any databases unless I specify localhost: before the file path or alias name.
What have I done wrong? The Firebird Book clearly states that this should be possible, and that it apparently should Just Work.
Thanks for any help that anyone can provide,
Best regards,
Dan.
I uninstalled FB superserver 1.5.1 and then installed a fresh copy of classic 1.5.2. I can now connect to databases, but only by using "localhost:". gsec is also unable to connect to the security database unless I use the -database=localhost:"c:\Program Files\firebird\firebird_1_5\security.fdb" switch. isql also cannot connect to any databases unless I specify localhost: before the file path or alias name.
What have I done wrong? The Firebird Book clearly states that this should be possible, and that it apparently should Just Work.
Thanks for any help that anyone can provide,
Best regards,
Dan.