Abstract: A process for performing a transaction, such as a write operation, on a data object in a non-log based database is described. An information storage and retrieval system described can execute a transaction at a speed limited only by the hardware of the system. Updates to the data are done in sequential block writes which allow the data to be written continually to memory. This allows for real-time feed of large blocks of data, such as Web content of all types, into the database. The process described allows for handling large data updates in the same manner as small data updates. An entry for a data object containing version data for the data object is created and maintained in an object table. This entry for the data object is written or saved to a non-persistent memory, such as a cache memory at a particular non-persistent memory address. This write operation is then committed by saving the data object in a persistent memory area at a persistent memory area address.

Abstract: A technique for stabilizing and collecting data in an information storage and retrieval system, referred to as checkpointing, is described. Checkpointing is used to increase the speed of the database during a recovery by only scanning data that the information storage and retrieval system knows is unstable, instead of scanning all the data in the database. Data that is deemed collectable, such as old data or obsolete data, is identified in a non-persistent memory space, such as a cache memory. A data page contained in an initial or first buffer is stored, also in the form of a data page, to a persistent memory type, such as a hard drive or virtual memory. Next, non-collectable data, or data that is to be maintained, in the initial or first buffer is identified. This data is stored in a second buffer. It is then determined whether the non-collectable data is referenced in an object table in the information storage and retrieval system.

Abstract: A technique for recoving a database having intrinsic versioning and no logging mechanism is described. The process allows the information storage and retrieval system to recover from crashes in very short times irrespective of the size and complexity of the data objects contained in the database. The recovery process does not require an update or transaction log, consequently all the delays associated with keeping a log, such write time to a log and log truncation during recovery are avoided. The most recent stable object table in the database is identified in a non-persistent memory storage area. An allocation map is then used to identify unstable data in the non-persistent memory area. The unstable data is then scanned to build a post-recovery object table. By performing this scan before a database crash or failure, a recovery can be performed without having to scan the non-persistent or the persistent memory areas of the information storage and retrieval system.

Abstract: A technique is disclosed for implementing collection of obsolete object versions stored in an information storage and retrieval system. The information storage and retrieval system includes persistent memory configured or designed to store a plurality of different object versions. The information storage and retrieval system further includes volatile memory which may be configured to store an object table which includes object version information relating to the plurality of object versions. The object version information includes information relating to locations in the persistent memory where each of the plurality of object versions are stored. A version collection procedure is initiated. At least one object version may then be identified as an obsolete object version without performing a memory access operation to the persistent memory to retrieve information relating to the at least one object version.

Abstract: A technique is disclosed for implementing system modification operations in an information storage and retrieval system. The information storage and retrieval system includes persistent memory configured or designed to store object data. The persistent memory includes at least one data file for storing object data. A first system modification request relating to a first data file is received, the first data file including a first object stored therein. The first system modification request is then implemented. According to a specific embodiment, the implementation of the first system modification request includes suspending write access to the first data file. Concurrently, while the first system modification request is being implemented, updated information relating to the first object may be stored in the persistent memory. According to a specific embodiment, the information storage and retrieval system corresponds to a non-positional, non-log based information storage and retrieval system.