Subject | Transaction ID overflow |
---|---|
Author | Brian Dunstan |
Post date | 2018-05-01T07:19:05Z |
Hi,
We have a big customer here who processes large numbers of transactions into a large database and plans to not backup and restore.
We are using Dialect 3. I think that means that the TID is 32 bits. I think that means they get 4,294,967,296 transactions before overflow - I'm assuming the TID is an unsigned integer. Is that correct?
If we move to dialect 3, does the TID become 64 bits?
Thanks,
Brian
[cid:image004.png@01D39141.C966B6D0]Brian Dunstan, CHIA
Technical Lead
Telstra Health - Communicare
M +61 419 906 150
E brian.dunstan@...<mailto:brian.dunstan@...>
W www.telstrahealth.com<http://www.telstrahealth.com/>
This email may contain confidential information.
If I've sent it to you by accident, please delete it immediately
[Non-text portions of this message have been removed]
We have a big customer here who processes large numbers of transactions into a large database and plans to not backup and restore.
We are using Dialect 3. I think that means that the TID is 32 bits. I think that means they get 4,294,967,296 transactions before overflow - I'm assuming the TID is an unsigned integer. Is that correct?
If we move to dialect 3, does the TID become 64 bits?
Thanks,
Brian
[cid:image004.png@01D39141.C966B6D0]Brian Dunstan, CHIA
Technical Lead
Telstra Health - Communicare
M +61 419 906 150
E brian.dunstan@...<mailto:brian.dunstan@...>
W www.telstrahealth.com<http://www.telstrahealth.com/>
This email may contain confidential information.
If I've sent it to you by accident, please delete it immediately
[Non-text portions of this message have been removed]