When you have data ready and it's checked to be correct and you insert it
into database, why it's bad idea to commit it?

You have correct data to use for other users (ie reporting).

And believe me customers like this property.



This place is "worst case" and amount of transactions is actually not the
point.

Point is how to reset counters.



We even don't know locations of all the places.

Some of the places do not have IT-persons or person who has some (deep)
experience about computers.



So you have to think that you can't get any help of these places.



By the way this has been only major problem in all these years .

So I think that how the programs works is planned very carefully.



Is this kind resetting property planned to include any release?



-br-

Petri



From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Vlad Khorsun
Sent: 1. syyskuuta 2009 19:08
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Re: Memory problem, isc_attach_database
failed

> Back to the basics. How can we avoid this kind of situation.
>
> Places are 24/7 and we don't know when those places have breaks to make
> backup/restore.

Your database was created near 2 years ago. I.e. your application generated
2147483646 transactions in less than 800 days. Or more than 2.6 mln tx per
day,
or more than 111K tx per hour, or almost 2K tx per minute. How do you create
such load ? Are you really need such crazy amount of transactions ? Think
about
it, improve your application and forget about the issue.

> So how can we reset transaction counters without use backup/restore.

No direct way.

Regards,
Vlad





[Non-text portions of this message have been removed]