Re: [firebird-support] Re: Rename database command
From my little knowlegde i would guess Robert is talking about the delta between the oldest active transaction and next transaction. But as long as i do not know anything about the application (event listeners, long time transactions and that) and the environment (Number of active connections and that) Robert writes about (may be he has in an earlier post) , it is just peeking around. just my EUR 0,02, Marcus Alexandre Benson Smith wrote: Em 5/6/2013 13:33, Leyne, Sean escreveu: Alexandre, While I completely agree with your points. I read the OP as meaning that they are running out of transactions ID (given the current 2GB limit) -- they have an 800GB database, so a large number of transactions would/could be expected, so transactions ID could get exhausted. In that case, a backup/restore would be required, but a weekly cycle is excessive (it means that the db is handling more than 3550 transactions per second!!! Very unlikely). Sean Hi Sean ! I read that, but the point I was talking about is related to this phrase: It became clear to us that to keep the system going we have to run a backup/restore every weekend because of slow downs when transaction counts got too high But I don't think that the transaction count getting too high would lead to a server slowdown. see you ! ++ Visit http://www.firebirdsql.org and click the Resources item on the main (top) menu. Try Knowledgebase and FAQ links ! Also search the knowledgebases at http://www.ibphoenix.com ++ Yahoo! Groups Links [Non-text portions of this message have been removed]
Re: [firebird-support] Re: Rename database command
Em 5/6/2013 17:34, Marcus Bajohr escreveu: From my little knowlegde i would guess Robert is talking about the delta between the oldest active transaction and next transaction. But as long as i do not know anything about the application (event listeners, long time transactions and that) and the environment (Number of active connections and that) Robert writes about (may be he has in an earlier post) , it is just peeking around. just my EUR 0,02, Marcus yep... that *would* cause slowndown... but back-up/restore is not needed to fix it. In fact.. the fix is in the application (transaction control), and if the application could not be fixed a simple SWEEP (gfix -sweep) would fix that if run when no one is connected (I assume that it is possible since he could back-up/restore) see you !
[firebird-support] Re: Rename database command
Hi Sean, While I don't pretend to understand Firebird at the atomic level. I am just trying to cope with database slowdowns. We find the only bullet proof methodology to solve database slowdowns is a backup restore. So we are searching for a method to be able to resolve database slowdowns, while keeping the database online. I am not concerned with whether theoretically firebird should or should not require a backup/restore. It seems that in practice under large database conditions to be a requirement. Our networks guy is going to spend some time seeing if he can give evidence of this requirement. Of course we will try any method to attempt to resolve this. In the past we have not found sweeping the database to help, but we will continue to do everything we can to resolve this for our customers sake. Kind Regards, Robert
