What are the important properties a schedule of transactions must have to maintain a database in a consistent state?
- is serializable
- a concurrent schedule which produces same result as a serial schedule is called serializable schedule
- is recoverable
- a schedule with the ability to recover from failures
- is cascadeless
- a schedule that avoids/eliminates cascading rollback in case of aborting of one or more transactions.
- preserves the order of the operations in each of the individual transactions
important properties of schedules in dbms
why a schedule need to be serializable
preserving the consistency of a database