Hey guys.
We have a webcluster consisting of 8 webservers running a PHP application with
a firebird DB. The application have a rather hard peak one time a day and
firebird are not able to give us the firebird connections quick enough. When
the peak start we experience long responses and
Hello,
thank you for your helping hand, whether in English or german language J
I have change it, now the IDs were created by trigger. Only one disadvantage
arises, if the user deletes the last recordset and creates a new, the last
skipped now.
Best regards.
Olaf
Von:
Hi Ronnie,
You did not provide key characteristics of the server, database and
transaction statistics, so please don't expect that you will have
reasonable answer (load of RAM and CPU are not characteristics of the
server. People have various opinions about big' and small).
You also did not
On 9-12-2013 19:29, checkmail wrote:
I have change it, now the IDs were created by trigger. Only one
disadvantage arises, if the user deletes the last recordset and creates
a new, the last skipped now.
Why is that a disadvantage? Holes in your numbering would also happen if
a user deleted a
Hi there,
nobody replied to the questions I asked about the Firebird system
tables some days ago. Maybe they were a bit too lengthy and specific.
I am wondering if anybody could point me to some documentation
regarding the Firebird system tables instead, as I could not find any.
Kind
10.12.2013 03:58, Christian Gütter wrote:
nobody replied to the questions I asked about the Firebird system
tables some days ago. Maybe they were a bit too lengthy and specific.
I am wondering if anybody could point me to some documentation
regarding the Firebird system tables instead,
