> Ivan Prenosil wrote:
> >
> >
> > >> > And what happen on rollover ?
> > >>
> > >> You can't start any new transactions - which is a pretty serious
> > >> problem when you need to use one to make backup to restore.
> > >>
> > >> Adam
> > >
> > > I imagine that's a case for IBSurgeon? They'd be able to rescue that
> > > wouldn't they?
> > > Alan
> >
> > What I would try in such case - set database to read only,
> > and lower next transaction value a bit (in db header, using hex editor)
> >
> > Ivan
> >
>
> It looks dangerous with 100- 200 concurrent connections on single
> database working 24/7 / What else besides backup/restore cycle could be
> done ? I planned to do backup of my database weekly,but not full restore
> only control restore to validate backup integrity.I seems that I need
> to change my plans.
> Maybe nbackup could allow (with new switch) to reset this counter ? but
> is this even possible ?
>
>
> Regards
> Boguslaw

please think again about this... even 100-200 concurrent connections 24/7 will find it very difficult to achieve 100 transactions per second. You'd be lucky to be getting 5-10 transactions per second. This would give you about 15 years worth. In reality, you may only have 1 transaction per second on an average 24 hours which gives you 100 years.
Do a check for your own beneift. Do a show database and see what TransID it is then wait 7 days and do another one and divide by 600,000. That's how to see the true average transactions per second.
Alan