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. > > > > I can't see a reason why transaction count (transaction ID) getting high would > make the engine slower...
> The back-up/restore could in fact make you database faster, but it has > nothing to do with the transaction counter being reset. 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
