Em 4/6/2013 22:23, sir_wally_lewis escreveu:
> 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 which means the system is barely keeping it's head above water.
>
I can't see a reason w
Alexandre,
> Em 4/6/2013 22:23, sir_wally_lewis escreveu:
> > 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 which means the system is barely keeping it's head
> above water.
> >
>
>
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
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 a
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) an
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, whil
Hi Robert,
what you can do for your own information:
query the database headers per:
gstat -h
that shows you the relevant transaction informations, and also if the
internal housekeeping (sweeping) is activated - and when, at what
interval (delta between oldest active transaction and oldest sn
This is probably a question for Stack Overflow, but I would like a Firebird
specific answer so asking here.
I would like to store simple documents in a Firebird database as an ordered
collection of paragraphs as follows:
Document 1
Record 1 -> 1. Heading 1
Record 2 -> 1.1 Heading 2
Record 3 ->
