Many applications need the generation of sequence numbers for each transaction to function properly.
The majority of database systems offer built-in sequence counters that are not locked in a two-phase manner; instead, when a transaction requests a sequence number, the counter is locked, increased, and unlocked in the same transaction.
Provide an explanation for why there may be gaps in the sequence numbers associated with the final set of committed transactions.
Already registered? Login
Not Account? Sign up
Enter your email address to reset your password
Back to Login? Click here