Subject | Questions about firebird.msg |
---|---|
Author | Daniel Albuschat |
Post date | 2009-07-30T07:06:21Z |
Hello,
I have a few questions about the firebird.msg file. At the site of one
of our clients, Firebird 1.5.5 (after doing a plain install) doesn't
find that file. You can see in the error message (e.g. when an
incorrect statement is executed) that it tries to open the file as
\\server-name\firebird.msg, while this obviously does not exist.
Does the client (this is not embedded) access the firebird.msg file at
all, or only the server?
How does Firebird look for that msg-file and can I probably set it to
a fixed path in the configuration?
We have quite a speed-problem on that site, which we believe
originates from Firebird trying to open a non-existing file on a
non-existing network-path, which slows down the whole process. To
clarify: In that particular situation where the program is slow, it
tries to find out certain information by blindly executing statements
which may be incorrect, which results in Firebird trying to generate
error messages a few times. And that part of the program takes 2.5
seconds on the client's site, while it is usually < 0.1 seconds in our
test-environments.
Kind regards,
Daniel Albuschat
I have a few questions about the firebird.msg file. At the site of one
of our clients, Firebird 1.5.5 (after doing a plain install) doesn't
find that file. You can see in the error message (e.g. when an
incorrect statement is executed) that it tries to open the file as
\\server-name\firebird.msg, while this obviously does not exist.
Does the client (this is not embedded) access the firebird.msg file at
all, or only the server?
How does Firebird look for that msg-file and can I probably set it to
a fixed path in the configuration?
We have quite a speed-problem on that site, which we believe
originates from Firebird trying to open a non-existing file on a
non-existing network-path, which slows down the whole process. To
clarify: In that particular situation where the program is slow, it
tries to find out certain information by blindly executing statements
which may be incorrect, which results in Firebird trying to generate
error messages a few times. And that part of the program takes 2.5
seconds on the client's site, while it is usually < 0.1 seconds in our
test-environments.
Kind regards,
Daniel Albuschat