This website uses cookies to ensure you get the best experience.
Learn more.
A design uses a SQL sequence and requires permanently gap-free business numbers even after rollbacks. What should be explained?
Published
- Naming the sequence GapFree enforces the requirement
- Every rollback necessarily returns all sequence values for reuse
- Sequence values are file backups
- Sequence allocation is not a guarantee of gap-free committed numbering
Comments — 0
Sign in to comment