TECHNICAL FIELD

The present invention relates generally to databases and, more particularly, to accessing data in a multi-generation database.

BACKGROUND

A database refers to an organized collection of data stored in a data storage system managed by a database management system (DBMS). The DBMS usually implements some type of synchronization to allow concurrent accesses to data in the database.

Synchronization may involve implementing a lock for each data in a database. If the locks are stored in high-speed memory, however, there may be scalability problems depending on the size of the database since high-speed memory tends to be small. On the other hand, storing the locks in a dedicated location in slow-access memory negatively impacts performance.

In a multi-generation database, data is organized according to one or more generations, or periods of time. One generation may end and another generation may begin at a checkpoint, at a restoration point, at the start of a particular operation, or at some other designated point in time.

Typically, there are multiple versions of each data, one for each generation. Each version is associated with a generation such that the newest version may be identified by searching for the version associated with the most current generation. Unfortunately, searching all the versions for the version with the most current generation is inefficient and makes synchronization difficult.

Systems and methods are needed to overcome the above-mentioned shortcomings. SUMMARY

The present disclosure is directed to systems and corresponding methods that facilitate accessing data in a multi-generation database.

For purposes of summarizing, certain aspects, advantages, and novel features have been described herein. It is to be understood that not all such advantages may be achieved in accordance with any one particular embodiment. Thus, the claimed subject matter may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages without achieving all advantages as may be taught or suggested herein.

In accordance with one embodiment, a method for accessing data in a multi-generation database is provided. The method comprises receiving a request to access first data in the database, wherein the first data is located on a first page of the database; reading an entry corresponding to the first page to locate a first track on the first page to access a newest version of the data; acquiring a first lock to synchronize accesses to the first track; and determining that the first track stores the newest version of the data, in response to reading the entry while holding the first lock.

In accordance with another embodiment, a system comprising one or more logic units is provided. The one or more logic units are configured to perform the functions and operations associated with the above-disclosed methods. In accordance with yet another embodiment, a computer program product and a computer program comprising a computer useable medium having a computer readable program is provided. The computer readable program when executed on a computer causes the computer to perform the functions and operations associated with the above-disclosed methods.

One or more of the above-disclosed embodiments in addition to certain alternatives are provided in further detail below with reference to the attached figures. The invention is not, however, limited to any particular embodiment disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described, by way of example only, with reference to preferred embodiments, as illustrated in the following figures:

FIG. 1 illustrates an exemplary database layout for a multi-generation database, in accordance with one or more embodiments;

FIG. 2 illustrates an exemplary page table to identify the newest version of data, in accordance with one embodiment;

FIG. 3 is a flow diagram of a method for reading data from a multi-generation database, in accordance with one embodiment;

FIG. 4 is a flow diagram of an exemplary method for identifying the newest version of data, in accordance with one embodiment;

FIG. 5 is a flow diagram of a method for writing data to a multi-generation database, in accordance with one embodiment;

FIG. 6 is a flow diagram of a method for advancing a page in a multi-generation database, in accordance with one embodiment; and

FIGS. 7 and 8 are block diagrams of hardware and software environments in which a system of the present invention may operate, in accordance with one or more embodiments.

Features, elements, and aspects of the invention that are referenced by the same numerals in different figures represent the same, equivalent, or similar features, elements, or aspects, in accordance with one or more embodiments. Detailed Description of the Invention

In the following, numerous specific details are set forth to provide a thorough description of various embodiments of the invention. Certain embodiments of the invention may be practiced without these specific details or with some variations in detail. In some instances, certain features are described in less detail so as not to obscure other aspects of a preferred embodiment of the invention. The level of detail associated with each of the elements or features should not be construed to qualify the novelty or importance of one feature over the others.

Referring to FIG. 1, in accordance with one embodiment, an exemplary multi-generation database 100 comprises one or more pages corresponding to data stored in the database 100. The database 100 may, for example, comprise N data such that there are N pages, one for each data. Each page of data comprises one or more versions of the data, wherein each version of the data is located on a different track, or location, on the page. For example, page 1 may comprise versions A, B, and C located on tracks 1, 2, and 3, respectively; and page 2 may comprise versions D, B, and C located on tracks 1, 2, and 3, respectively.

The database 100 is managed by a DBMS 110. In particular, the DBMS 110 manages access to data in the database 100. To do so, the DBMS 110 may synchronize access to data by implementing a lock for each track of each page in the database 100. For read accesses, the lock may be shared by more than one access. For write accesses, the lock is exclusive to one access. Desirably, the lock is stored on the track with the data so that one access is sufficient to access both the lock and the version of the data on the track, improving performance and providing scalability for large databases. In one embodiment, locks on the same page may be collectively treated as a single lock.

The DBMS 110 may also maintain a page table to locate the newest version of data on a page. Maintaining the page table improves performance and simplifies synchronization by removing the need to search each version of the data to find the newest version. Referring to

FIGS. 1 and 2, in accordance with one embodiment, an exemplary page table 200 comprises one or more entries corresponding to one or more pages of the database 100. For example, the page table 200 may comprise N entries corresponding to N pages of the database 100. Each of the entries refers to the track of the newest version of the data stored on the page associated with the entry.

Depending on implementation, different formats may be used to refer to a track. Desirably, a minimal number of bits are used to provide scalability for large databases. For example, approximately log ₂ (N) bits may be used to refer to a track if there are N tracks on a page. In the exemplary illustration in FIG. 1, the newest version of the data on page 1, version C, is located on track 3; and the newest version of the data on page 2, version D, is located on track 1. Since there are 3 tracks on a page, two bits are used to refer to a track. "00" is used to refer to track 1, "01" is used to refer to track 2, and "10" is used to refer to track 3, for example.

Referring to FIGS. 1 and 3, in accordance with one embodiment, the DBMS 110 receives a request to access data located on a first page of the database 100 (P300). In response, the

DBMS 110 reads an entry corresponding to the first page from page table 200 to locate a first track on the first page storing the newest version of the data (P310). For example, if the DBMS 110 receives a request to access data from page 1 of the database 100, the DBMS 110 reads entry 1 from page table 200. In FIGS. 1 and 2, entry 1 refers to track 3 storing version C of the data.

Upon locating the first track, the DBMS 110 acquires a lock to synchronize accesses to the first track (P320). The lock synchronizes accesses to the data such that the newest version of the data is located on the first track as long as the entry refers to the first track while the lock to the track is held. Once the lock to the first track is acquired, the entry is read a second time to determine whether the newest version of the data is still located on the first track (P330).

The entry may change between the first reading and the second reading if the first page comprising the data is advanced to a new generation after the first reading but before acquiring the lock to the first track. Further details on advancing the page are provided below with reference to FIG. 6. If the newest version of the data is still located on the first track (P340), the DBMS returns the version of the data located on the first rack (P350). If the newest version of the data is no longer located on the first track (P340), the DBMS 110 releases the lock (P360) and repeats P310 through P360.

Referring to FIGS. 1, 3, and 4, in accordance with one embodiment, the DBMS 110 receives a request to read data located on a first page of the database 100 (P400). Upon receiving the request, the DBMS 110 accesses a first track on the first page storing the newest version of the data (P410, P300-350) and returns the newest version of the data (P420). The DBMS 110 also releases the lock to the first track that was acquired during P410 (P430).

Referring to FIGS. 1, 3, and 5, in accordance with one embodiment, the DBMS 110 receives a request to update data located on a first page of the database 100. Upon receiving the request, the DBMS 110 accesses a first track on the first page storing the newest version of the data (P500, P300-350) and determines whether the first track is associated with the current generation (P520). The DBMS 110 may identify the current generation, for example, by checking recent transactions in a transaction log maintained by the DBMS 110.

If the first track is associated with the current generation (P520), the DBMS 110 writes to the first track, updating the newest version of the data (P530), and then releases the lock to the first track (P540), which was exclusively acquired during P500. Otherwise, the DBMS 110 advances the first page to the current generation (P550) and writes to a second track on the first page, updating the newest version of the data (P560). Advancing the first page, which includes creating a new version of the data on the second track and updating the page table 200, is done atomically from a user perspective.

Referring to FIGS. 1, 5, and 6, in accordance with one embodiment, the DBMS 110 creates a copy of the newest version of the data (P600). If an unused second track is available on the first page (P610), the DBMS 110 stores the copy on the unused second track (P620). Otherwise, the DBMS 110 stores the copy on a used second track by overwriting the oldest version of the data (P630). In one embodiment, the oldest version of the data is located on the track to the right of the newest version of the data. For example, in FIGS. 1 and 2, since version C is the newest version of the data on page 1, the oldest version of the data is version A, located on track 1 (with overlap).

Once the newest version of the data is copied to the second track, the second track is associated with the current generation (P640), and the lock synchronizing accesses to the second track is reset and exclusively acquired (P650). Thus, the copy of the newest version of the data stored on the second track becomes the newest version of the data.

Referring back to FIGS. 1, 5, and 6, on acquiring the lock to the second track, the DBMS 110 updates the entry for the page in page table 200 (P660) and releases the lock to the first track that was exclusively acquired during P500 (P670). Once the entry is updated, the DBMS 110 writes to the second track, updating the newly created newest version of the data (P680, P560) and releases the lock to the second track (P690). For example, if page 1 is advanced, page 1 of FIG. 1 and entry 1 of FIG. 2 become like page 2 of FIG. 1 and entry 2 of FIG. 2.

In different embodiments, the invention may be implemented either entirely in the form of hardware or entirely in the form of software, or a combination of both hardware and software elements. For example, database 100 and DBMS 110 may be included in a controlled computing system environment that can be presented largely in terms of hardware components and software code executed to perform processes that achieve the results contemplated by the system of the present invention.

Referring to FIGS. 7 and 8, a computing system environment in accordance with an exemplary embodiment is composed of a hardware environment 1110 and a software environment 1120. The hardware environment 1110 comprises the machinery and equipment that provide an execution environment for the software; and the software provides the execution instructions for the hardware as provided below.

As provided here, the software elements that are executed on the illustrated hardware elements are described in terms of specific logical/functional relationships. It should be noted, however, that the respective methods implemented in software may be also implemented in hardware by way of configured and programmed processors, application specific integrated circuits (ASICs), Field Programmable Gate Arrays (FPGAs) and digital signal processors (DSPs), for example.

Software environment 1120 is divided into two major classes comprising system software

1121 and application software 1122. System software 1121 comprises control programs, such as the operating system (OS) and information management systems that instruct the hardware how to function and process information.

In one embodiment, DBMS 110 is implemented as application software 1122 executed on one or more hardware environments to manage access to the database 100. Application software 1122 may comprise but is not limited to program code, data structures, firmware, resident software, microcode or any other form of information or routine that may be read, analyzed or executed by a microcontroller.

In an alternative embodiment, the invention may be implemented as computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer-readable medium may be any apparatus that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus or device.

The computer-readable medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk read only memory (CD-ROM), compact disk read/write (CD- R/W) and digital video disk (DVD).

Referring to FIG. 7, an embodiment of the application software 1122 may be implemented as computer software in the form of computer readable code executed on a data processing system such as hardware environment 1110 that comprises a processor 1101 coupled to one or more memory elements by way of a system bus 1100. The memory elements, for example, may comprise local memory 1102, storage media 1106, and cache memory 1104. Processor 1101 loads executable code from storage media 1106 to local memory 1102. Cache memory 1104 provides temporary storage to reduce the number of times code is loaded from storage media 1106 for execution.

A user interface device 1105 (e.g., keyboard, pointing device, etc.) and a display screen 1107 can be coupled to the computing system either directly or through an intervening I/O controller 1103, for example. A communication interface unit 1108, such as a network adapter, may be also coupled to the computing system to enable the data processing system to communicate with other data processing systems or remote printers or storage devices through intervening private or public networks. Wired or wireless modems and Ethernet cards are a few of the exemplary types of network adapters.

In one or more embodiments, hardware environment 1110 may not include all the above components, or may comprise other components for additional functionality or utility. For example, hardware environment 1110 can be a laptop computer or other portable computing device embodied in an embedded system such as a set-top box, a personal data assistant (PDA), a mobile communication unit (e.g., a wireless phone), or other similar hardware platforms that have information processing and/or data storage and communication capabilities.

In some embodiments of the system, communication interface 1108 communicates with other systems by sending and receiving electrical, electromagnetic or optical signals that carry digital data streams representing various types of information including program code. The communication may be established by way of a remote network (e.g., the Internet), or alternatively by way of transmission over a carrier wave.

Referring to FIG. 8, application software 1122 may comprise one or more computer programs that are executed on top of system software 1121 after being loaded from storage media 1106 into local memory 1102. In a client-server architecture, application software 1122 may comprise client software and server software. For example, in one embodiment, client software is executed on a general computing system and server software is executed on a server system.

Software environment 1120 may also comprise browser software 1126 for accessing data available over local or remote computing networks. Further, software environment 1120 may comprise a user interface 1124 (for example, a Graphical User Interface (GUI)) for receiving user commands and data. Please note that the hardware and software architectures and environments described above are for purposes of example, and one or more embodiments of the invention may be implemented over any type of system architecture or processing environment.

It should also be understood that the logic code, programs, modules, processes, methods and the order in which the respective steps of each method are performed are purely exemplary. Depending on implementation, the steps can be performed in any order or in parallel, unless indicated otherwise in the present disclosure. Further, the logic code is not related, or limited to any particular programming language, and may comprise of one or more modules that execute on one or more processors in a distributed, non-distributed or multiprocessing environment.