In a Main Memory Database (MMDB) the primary copy of the database resides in volatile main memory. This makes MMDB systems more vulnerable to failures compared to the traditional Disk Resident Databases (DRDB). A backup copy of the database is maintained in secondary storage for recovery purposes. Recovery activities like logging, checkpointing and reloading are used to restore the database to aconsistent state after a system crash has occurred.In this paper, we focus on two points. Firstly we examine MMDB logging, checkpointing and reloading activeities. Secondly, we implement a recovery scheme with transaction consistent checkpointing for a main memory database. |