How are transactions handled by personal and client/server databases in case of a failure?
What will be an ideal response?
In the personal database environment, when a client performs data manipulation
on records, the records are locked the client’s changers are not available to the
other clients. If the client system fails due to hardware or software malfunction,
the locked records stay locked and the transactions in progress are lost. The
transaction log is in the client’s computer, which is lost. In many cases, the
database gets corrupted. The repair can be performed after all the logged in users log off of the system. If the database is not repairable, all the transactions after the last backup are also lost.
In the client/server database environment, failure of a client does not affect other
clients. The failed client’s transactions in progress are lost, but the transaction log
is not lost as it is kept on the server. The Database Administrator can decide to
rollback unfinished transactions and inform client to resubmit transactions later.
You might also like to view...
Which of the following XML based markup languages provides a protocol for business transactions on the Internet?
(a) BML. (b) cXML. (c) CML. (d) SMIL.
Why might you want to use a RAID 0 disk configuration?
A. to improve overall disk performance B. RAID 0 drives are less expensive than other RAID drives C. to prevent data loss in case of a drive failure D. because RAID 0 provides an automatic disk backup