Abstract
The current approach to handle interleaved write operation and preserve consistency in relational database system still relies on the locking protocol. If any entity is locked by any transaction, then it becomes temporary unavailable to other transaction until the lock is released. The temporary unavailability can be more often if the number of write operation increases as happens in the application systems that utilize IoT technology or smartphone devices to collect the data. To solve this problem, this research is proposed blind write protocol which does not lock the entity while the transaction is performing a write operation. This paper presents the basic principles of blind write protocol implementation in a relational database system
Highlights
Current implementation of concurrency control in Relational Database Management System (RDBMS) [1] handles the interleaved operations and temporary inconsistent at the database system level
This paper proposes blind write protocol (BWP) as a complement to the current concurrency control to be applied in the RDBMS
If the write operations are using constant or fix value they can use blind write protocol which does not lock the entity. This approach can prevent unnecessary temporary unavailable situation and prevent unnecessary waiting. It increases the availability of entity
Summary
Current implementation of concurrency control in Relational Database Management System (RDBMS) [1] handles the interleaved operations and temporary inconsistent at the database system level. The last two approaches are proposed to achieve more on availability These 3 concurrency controls above are handling the interleaved write operations at the system level. Some of the write operation depend on the current or other entity value, e.g. withdraw or deposit operation to the bank account To perform these operations, the concurrency control should use locking protocol to achieve consistency and prevent the concurrency anomaly. If the write operations are using constant or fix value they can use blind write protocol which does not lock the entity. This approach can prevent unnecessary temporary unavailable situation and prevent unnecessary waiting.
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call