Hi,

If it is automatically restarted even persistent connections exists then i see 
no problem. We do not have queries open for month ;-)

I ask because i am warried that this work in the same way as transaction id - 
after reach max int system stop and only backup restore can help. But here we 
have not this problem i am glad to heare this.

Ps. We have not any maitenance hours ;-) this is safer then stop something 
which work ok years. I see in my life that after restart some systems can not 
start but without this it work ok.  Also replace some old good working hardware 
by new is risk. We prefere to have new server ready to work if old server 
crash. And we change old to new server only if we reach some hardware limit

Regards,
Karol Bieniaszewski

----- Reply message -----
Od: "Dmitry Yemanov" <[email protected]>
Do: <[email protected]>
Temat: Odp: [firebird-support] Re: MON$STATEMENTS - RDB$STATEMENT_ID - Integer?
Data: pt., sty 3, 2014 07:55
03.01.2014 09:14, [email protected] wrote:

>

> But what happen if to database is always someone connected? This is 24/7

> software.



Basically, I don't believe in databases working 24/7 for years without 

dedicated maintenence hours ;-)



But even in this case, the statement ID counter will wrap around and 

restart one day without any issues. It's not used internally for 

anything other than monitoring and I really doubt that your software 

will have queries open for months.



Dmitry









Reply via email to