US20050055385A1 - Querying past versions of data in a distributed database - Google Patents
Querying past versions of data in a distributed database Download PDFInfo
- Publication number
- US20050055385A1 US20050055385A1 US10/866,333 US86633304A US2005055385A1 US 20050055385 A1 US20050055385 A1 US 20050055385A1 US 86633304 A US86633304 A US 86633304A US 2005055385 A1 US2005055385 A1 US 2005055385A1
- Authority
- US
- United States
- Prior art keywords
- data
- database
- processors
- computer
- past version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99954—Version management
Definitions
- 60/500,509 entitled “System, Structure, Interface, and Semantics For Implementing Row Versions: Accessing Past Versions Of A Data Item”
- U.S. Provisional Patent Application No. 60/500,510 entitled “Method and Mechanism For Row Versioning”; the contents of all of which are incorporated by this reference in their entirety for all purposes as if fully set forth herein.
- the present invention relates generally to database systems and, more specifically, to techniques for querying past versions of data from a remote database in a distributed database system.
- Temporal database access provides the capability to access data from a database, that reflects the state of the data at any given time in the life of the data. Temporal database access can support recovery at all levels, including the row, transaction, table, tablespace, and database wide levels, and is often used to correct human errors by reconstructing data as the data was in the past.
- Temporal database access technology has evolved over the years.
- temporal access is enabled for a user session, through which a user can “see” the entire database at a particular point in time in the past (referred to as a “flashback query”).
- flashback query a point in time in the past
- This technology allows a user to query data as it was in the past, without having to persistently rollback changes that were made to the data from the time in the past up to the time of the query (which can take hours or days to complete).
- this incarnation allows for a speedy method for point-in-time recovery, like having a rewind button for the database.
- flashback queries specify a flashback time, and return data as it existed at the specified flashback time.
- One technique for handling flashback queries is described in U.S. Pat. No. 6,631,374 entitled “System And Method For Providing Fine-Grained Temporal Database Access” by Jonathan D. Klein, et al., the contents of which is incorporated by this reference in its entirety for all purposes as if fully set forth herein.
- temporal access enables a user to query particular data at multiple particular points in time in the past. For example, a user can query and manipulate data from a table T1 at a time t1, data from a table T2 at a time t2, data from a table T3 at present time, and so on, while maintaining referential integrity constraints among the tables.
- the granularity of the temporal access evolved from entire database access at a particular time in the past, to particular table access at particular points in time in the past, like having a rewind button for each of the tables in the database.
- temporal access enables a user to query particular data over a range of time, rather than at a point in time.
- a user can query and manipulate multiple versions of data at the row level.
- the reach of the temporal access evolved from accessing the state of data at a point in time to the progression of data over a span of time.
- transaction metadata is returned for transactions that occurred on the specified data over the specified range of time, such as metadata that identifies what transactions were committed and when.
- the current state of temporal database access is extended to provide fast and easy recovery at the database, table, row, and transaction level, and by just operating on the changed data. Therefore, data can be queried as it existed in the past, current data can be compared to past data, and deleted or changed data can be recovered. The time it takes to recover from an error is now equal to the amount of time it took to make the error.
- the time it takes to recover from an error is now equal to the amount of time it took to make the error.
- FIG. 1 is a block diagram that illustrates an operating environment in which an embodiment of the invention may be implemented
- FIG. 2 is a flow diagram that illustrates a method for managing requests for data, according to an embodiment of the invention.
- FIG. 3 is a block diagram that illustrates a computer system upon which an embodiment of the invention may be implemented.
- a request for data, in a past state, from a “remote” database can be received at a “local” database server. Relevant portions of the request are passed to the remote server, where the relevant portions are processed. The processing performed by the remote server includes returning the requested data in the specified past state to the local server, or at least returning enough information to reconstruct the data into the past state.
- “local” simply refers to the database server that receives the request, e.g., a database query, from a user; and “remote” simply refers to another database and/or server that is associated with the local server via a conventional distributed database link.
- a request for a past version of data includes a time-specifying parameter to specify the past version of the data, which may include a timestamp, a system change number that is used to track the sequence in which events occur within a database server, and the like.
- the time-specifying parameter may include a time interval with which the data is associated in the remote database, where multiple versions of the data are returned, or at least enough information to reconstruct the data into the past versions, each of which is associated with a time that falls within the time interval.
- Examples of the breadth of applicability of these techniques include application (1) to a distributed database system comprising many databases, (2) to database query operations on the past version of the data, (3) to database query operations on the past version of the data and a current version of the same or other data, from the same or another database, and (4) to database query operations on the past version of the data and the same or other data in a different past state, from the same or another database.
- FIG. 1 is a block diagram that illustrates an operating environment in which an embodiment of the invention may be implemented.
- the operating environment of FIG. 1 is referred to herein as a distributed database system (or, simply, a distributed database).
- a distributed database comprises a set of databases, each stored on different storage mechanisms, that appears to applications as a single database. Consequently, an application can simultaneously access and modify the data in several databases in a network.
- Each database in the system is controlled by its local database management server (DBMS) but cooperates to maintain the consistency of the global distributed database.
- DBMS database management server
- Distributed database 100 is illustrated as having three interconnected databases; however, a distributed database can generally comprise any number of interconnected databases. Thus, FIG. 3 depicts three databases simply for purposes of example and explanation.
- Distributed database 100 comprises a number of database servers (“server”) 102 a , 102 b , 102 c that are each communicatively connected to respective databases 104 a , 104 b , 104 c .
- the servers 102 a , 102 b , 102 c are communicatively connected to each other via one or more network 106 , such as a conventional LAN (Local Area Network), a WAN (Wide Area Network) such as the Internet, or both.
- network 106 such as a conventional LAN (Local Area Network), a WAN (Wide Area Network) such as the Internet, or both.
- the servers can exchange database statements such as standard SQL queries or portions thereof, and/or portions of a query execution plan.
- a database server 102 a , 102 b , 102 c is a combination of integrated software components and an allocation of computational resources (such as memory and processes) for executing the integrated software components on a processor, where the combination of the software and computational resources are used to manage a particular database, such as database 104 a , 104 b , 104 c .
- a database server typically governs and facilitates access to a database by processing requests from clients to access the database.
- each database server 102 a , 102 b , 102 c within distributed database 100 is communicatively connected to one or more client applications via one or more networks, such as a conventional LAN or WAN.
- the network(s) that connects client applications to the database servers may or may not be the same as network 106 , which interconnects the database servers.
- Client applications are typically software programs that request and possibly manipulate data, via a database server 102 a , 102 b , 102 c , that is stored in one or more of databases 104 a , 104 b , 104 c .
- Non-limiting examples of client applications include a web browser executing on a desktop computer and a more programmatically complex application program executing on an application server or other mid-tier component.
- Each server 102 a , 102 b , 102 c executes on a computer such as computer system 300 of FIG. 3 .
- a server in a distributed database system can act as a client, a server, or both.
- the server 102 a used to manage database 104 a is acting as a server when a statement is issued against its local data in database 104 a , and is acting as a client when it issues a statement against remote data in database 104 b.
- Each database 104 a , 104 c , 104 c is a repository for data and metadata that is stored on a persistent memory mechanism, such as a set of hard disks.
- data and metadata may be stored in each database logically, for example, according to relational database constructs, multidimensional database constructs, or a combination of relational and multidimensional database constructs.
- Each database 104 a , 104 c , 104 c in a distributed database 100 is distinct from all other databases in the system.
- Each database of a distributed database typically stores different data than the other databases in the system, i.e., the different databases are not simply back-ups of another database.
- each database 104 a , 104 b , 104 c may store data for a particular organizational group or function (e.g., Human Resources, Finance, Sales, Manufacturing) or may store data for different organizational regions or countries (e.g., Americas, Asia, Europe).
- each database has its own global database name which may, for example, be prefixed with an associated network domain name.
- servers 102 a , 102 b , 102 c are logically interconnected through database links.
- a database link defines a one-way communication path from a database system (e.g., a database server and a database) to another database system.
- server 102 a is associated with a database link 108 ab that points to server 102 b and, similarly, server 102 b is associated with a database link 108 ba that points to server 102 a .
- servers 102 b and 102 c have associated database links 108 bc , 108 cb ; and servers 102 a and 102 c have associated database links 108 ac , 108 ca .
- Database links are typically implemented to operate transparently to users, for example, by naming the database links the same as the global name of the database to which the link points.
- a database link may be a private database link in a specific schema of a local database, with which only the owner of the private database link or subprograms in the schema can use the private database link to access data and database objects in the corresponding remote database.
- a database link may be a public database link, with which all users and subprograms in the local database can use the public database link to access data and database objects in the corresponding remote database.
- a distributed database typically supports (1) remote queries, updates, and transactions which select or update information from one or more remote tables, all of which reside at the same remote node; (2) distributed queries, updates, and transactions, which select or update information from two or more nodes, each of which may be a local or a remote node.
- Client applications of a distributed database can make local procedure calls to perform work at a local database and remote procedure calls to perform work at a remote database, through which the local server passes all procedure parameters in the call to the remote server.
- Location transparency within a distributed database exists when a user can universally refer to a database object, such as a table, regardless of the node to which an application connects. Synonyms can be used to establish location transparency for the tables and supporting objects in an application schema, where synonyms are created in a local database for tables in a remote database. Consequently, rather than accessing a remote table using its actual database link path to the table, the remote table can be accessed using a much simpler query, using the synonym, that does not have to account for the table location.
- a distributed database such as distributed database 100 .
- FIG. 2 is a flow diagram that illustrates a method for managing requests for data, according to an embodiment of the invention.
- the illustrated method is performed by, for example, a database management server such as any of servers 102 a , 102 b , 102 c.
- a request is received at a first database server that manages a first database, where the request is for a past version of data that is stored in a second database that is managed by a second database server.
- the data is stored in a current state in the second database.
- the requested data is not also stored in the first database, such as in a redundant database architecture.
- the second database also stores enough information, such as metadata and transaction log files (e.g., undo and redo files), to reconstruct the past version of the data.
- a request is received at database server 102 a , via a network, from a user working at a web browser, where the request is for a past version of data that is stored in database 104 b.
- the database server that receives the original request from the client is referred to herein as the “local” server and the database managed by the local server is referred to herein as the “local” database; whereas any of the other database servers and databases in the distributed database system other than the local server and database are referred to herein as a “remote” server and a “remote” database, respectively.
- the past version of data that is requested at block 202 is specified, in one embodiment, by a time-specifying parameter within the request.
- the time-specifying parameter may specify a particular time that can be compared to a timestamp that is associated with the requested past version of data, and in another implementation, the time-specifying parameter may be a system change number (SCN) associated with a transaction on the requested data.
- SCN system change number
- the request specifies a point in time that can be used by the remote server to identify the past version of the data.
- the remote database in which the requested data is stored is specified in the request, by specifying the requested data in association with the relevant database link, or by specifying the requested data in conjunction with a synonym for the table that contains the data at the database link.
- the request received at block 202 specifies a time interval with which the data is associated in the second database. If there were multiple versions of the data during that time interval, then the request is for each of the multiple versions. What data is returned in response to this type of request is described in reference to block 206 .
- a multiplicity of data request types can be made.
- a query in conjunction with a request for a past version of data stored in a remote database, a query can be submitted to a database server that includes (1) a request for a current version of the same data represented in the requested past version, from the same remote database; (2) a request for a past version of different data from the same remote database; (3) a request for a past version of different data from a different database in the distributed database system, whether it be the local database or a different remote database; (4) a request for a current version of different data from a different database in the distributed database system, whether it be the local database or a different remote database; (5) a request for multiple past versions of the same data, at different points or intervals in time, from the same remote database; (6) a request for multiple past versions of different data, at the same or different points or intervals in time, from other database(s) in the
- the request received at block 202 may also specify a database operation to perform on the past data, such as a join of (a) a table that contains the past version of the data, with (b) a table that contains a past or current version of the same or other data; or may specify a past version of data in a subquery clause of a DML (data manipulation language) operation or DDL (data definition language) operation.
- a database operation to perform on the past data, such as a join of (a) a table that contains the past version of the data, with (b) a table that contains a past or current version of the same or other data; or may specify a past version of data in a subquery clause of a DML (data manipulation language) operation or DDL (data definition language) operation.
- DML data manipulation language
- DDL data definition language
- the past version of the data is requested from the second database server, in response to the request received at block 202 .
- local database server 102 a passes a portion of the query, or a portion of the query execution plan, to remote database server 102 b for retrieval of the requested past version of data from database 104 b.
- the optimizer recognizes that the query contains a request for data from a linked remote database 104 b , and causes at least a portion of the query or query plan which is relevant to the requested data to be passed to the remote server 102 b , where the portion is executed.
- Local server 102 a passes the portion to server 102 b via the network 106 .
- One technique for passing information that specifies the requested point or interval in time to the remote server 102 b is to pass the information to an API associated with the remote server, where the API allows the passing of and is able to handle such information.
- One other technique for passing such information to the remote server 102 b is to pass the information using a remote procedure call to a procedure that executes on the remote server.
- Use of the technique described is not limited to any particular approach to passing the time-specifying information from the local server to the remote server.
- the past version of the data is received at the first (i.e., local) database server from the second (i.e., remote) database server.
- Execution of the portion of the query or plan that was passed to the remote server at block 204 may vary from implementation to implementation. For example, what is performed at the remote server may entail simply accessing and returning to the local server the data and relevant metadata that can be used to reconstruct the past version of the data, or actually reconstructing the past version of the data.
- the past version of the data that is received at the local server at block 206 may comprise the data and relevant metadata that can be used to reconstruct the past version of the data by the local server, or a complete reconstructed past version of the data.
- the technique described allows a user to see the data in the past state without persistently transforming the data. Furthermore, a user can simply request the past version of data using a query represented in a conventional query language, such as SQL, without requiring the expertise of a database administrator.
- a query represented in a conventional query language such as SQL
- block 206 comprises receiving multiple versions of the data, each of which is associated with a time that falls within the specified time interval.
- what is received at the local server may be a past version and a current version of the data if the specified time interval ends with a current time (e.g., a time after which no transactions have committed changes on the requested data), or may be multiple past versions that are associated with respective database transactions that were committed on the requested data during the specified time interval.
- transaction metadata is received at the local server from the remote server, where the transaction metadata includes information that describes what database transactions were committed on the data during the specified time interval and when the transactions committed, which can be used to reconstruct the various versions of the data that existed at times within the time interval. This allows a user to see the progression of the data over the time interval.
- the method described in reference to FIG. 2 provides for querying, from a local server in a distributed database system, past versions of data from a remote server in the distributed database system, using temporal database access mechanisms.
- FIG. 3 is a block diagram that illustrates a computer system 300 upon which an embodiment of the invention may be implemented.
- Computer system 300 includes a bus 302 or other communication mechanism for communicating information, and a processor 304 coupled with bus 302 for processing information.
- Computer system 300 also includes a main memory 306 , such as a random access memory (RAM) or other dynamic storage device, coupled to bus 302 for storing information and instructions to be executed by processor 304 .
- Main memory 306 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 304 .
- Computer system 300 further includes a read only memory (ROM) 308 or other static storage device coupled to bus 302 for storing static information and instructions for processor 304 .
- a storage device 310 such as a magnetic disk, optical disk, or magneto-optical disk, is provided and coupled to bus 302 for storing information and instructions.
- Computer system 300 may be coupled via bus 302 to a display 312 , such as a cathode ray tube (CRT) or a liquid crystal display (LCD), for displaying information to a computer user.
- a display 312 such as a cathode ray tube (CRT) or a liquid crystal display (LCD)
- An input device 314 is coupled to bus 302 for communicating information and command selections to processor 304 .
- cursor control 316 is Another type of user input device, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 304 and for controlling cursor movement on display 312 .
- This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
- the invention is related to the use of computer system 300 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 300 in response to processor 304 executing one or more sequences of one or more instructions contained in main memory 306 . Such instructions may be read into main memory 306 from another computer-readable medium, such as storage device 310 . Execution of the sequences of instructions contained in main memory 306 causes processor 304 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
- Non-volatile media includes, for example, optical, magnetic, or magneto-optical disks, such as storage device 310 .
- Volatile media includes dynamic memory, such as main memory 306 .
- Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 302 . Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
- Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
- Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 304 for execution.
- the instructions may initially be carried on a magnetic disk of a remote computer.
- the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
- a modem local to computer system 300 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal.
- An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 302 .
- Bus 302 carries the data to main memory 306 , from which processor 304 retrieves and executes the instructions.
- the instructions received by main memory 306 may optionally be stored on storage device 310 either before or after execution by processor 304 .
- Computer system 300 also includes a communication interface 318 coupled to bus 302 .
- Communication interface 318 provides a two-way data communication coupling to a network link 320 that is connected to a local network 322 .
- communication interface 318 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line.
- ISDN integrated services digital network
- communication interface 318 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
- LAN local area network
- Wireless links may also be implemented.
- communication interface 318 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
- Network link 320 typically provides data communication through one or more networks to other data devices.
- network link 320 may provide a connection through local network 322 to a host computer 324 or to data equipment operated by an Internet Service Provider (ISP) 326 .
- ISP 326 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 328 .
- Internet 328 uses electrical, electromagnetic or optical signals that carry digital data streams.
- the signals through the various networks and the signals on network link 320 and through communication interface 318 which carry the digital data to and from computer system 300 , are exemplary forms of carrier waves transporting the information.
- Computer system 300 can send messages and receive data, including program code, through the network(s), network link 320 and communication interface 318 .
- a server 330 might transmit a requested code for an application program through Internet 328 , ISP 326 , local network 322 and communication interface 318 .
- the received code may be executed by processor 304 as it is received, and/or stored in storage device 310 , or other non-volatile storage for later execution. In this manner, computer system 300 may obtain application code in the form of a carrier wave.
Abstract
Description
- This application is related to U.S. Pat. No. 6,631,374 issued Oct. 7, 2003, entitled “System and method for providing fine-grained temporal database access”; U.S. patent application Ser. No. 10/364,209 filed Feb. 10, 2003, entitled “Method And Mechanism For Identifying Last Transaction On A Row of Data”; U.S. patent application Ser. No. 10/364,065 filed Feb. 10, 2003, entitled “Method And Mechanism For Rolling Back A Transaction On A Row of Data”; U.S. patent application Ser. No. 10/325,211 filed Dec. 18, 2002, entitled “Method And Apparatus For Accessing Data As It Existed At A Previous Point In Time”; U.S. Provisional Patent Application No. 60/500,509, entitled “System, Structure, Interface, and Semantics For Implementing Row Versions: Accessing Past Versions Of A Data Item”; U.S. Provisional Patent Application No. 60/500,510, entitled “Method and Mechanism For Row Versioning”; the contents of all of which are incorporated by this reference in their entirety for all purposes as if fully set forth herein.
- The present invention relates generally to database systems and, more specifically, to techniques for querying past versions of data from a remote database in a distributed database system.
- Temporal database access provides the capability to access data from a database, that reflects the state of the data at any given time in the life of the data. Temporal database access can support recovery at all levels, including the row, transaction, table, tablespace, and database wide levels, and is often used to correct human errors by reconstructing data as the data was in the past.
- Temporal database access technology has evolved over the years. In an early incarnation, temporal access is enabled for a user session, through which a user can “see” the entire database at a particular point in time in the past (referred to as a “flashback query”). Hence, a user can access the state of all the data in a database at any specified point in time. This technology allows a user to query data as it was in the past, without having to persistently rollback changes that were made to the data from the time in the past up to the time of the query (which can take hours or days to complete). Thus, this incarnation allows for a speedy method for point-in-time recovery, like having a rewind button for the database.
- Unlike conventional queries, flashback queries specify a flashback time, and return data as it existed at the specified flashback time. One technique for handling flashback queries is described in U.S. Pat. No. 6,631,374 entitled “System And Method For Providing Fine-Grained Temporal Database Access” by Jonathan D. Klein, et al., the contents of which is incorporated by this reference in its entirety for all purposes as if fully set forth herein.
- In another incarnation, temporal access enables a user to query particular data at multiple particular points in time in the past. For example, a user can query and manipulate data from a table T1 at a time t1, data from a table T2 at a time t2, data from a table T3 at present time, and so on, while maintaining referential integrity constraints among the tables. Thus, the granularity of the temporal access evolved from entire database access at a particular time in the past, to particular table access at particular points in time in the past, like having a rewind button for each of the tables in the database.
- One technique for identifying one or more transactions that have modified or created an object, such as a row of data, in a database system is described in U.S. patent application Ser. No. 10/364,209 filed by Ken Jacobs, et al. on Feb. 10, 2003, entitled “Method And Mechanism For Identifying Last Transaction On A Row of Data”; which incorporates by reference U.S. patent application Ser. No. 09/748,408 filed by Amit Ganesh, et al. on Dec. 22, 2000 and issued as U.S. Pat. No. 6,647,510, entitled “Method and Apparatus for Making Available Data that was Locked by a Dead Transaction before Rolling Back the Entire Dead Transaction”; the contents of all of which are incorporated by this reference in their entirety for all purposes as if fully set forth herein.
- One technique for undoing, reversing, or compensating for a committed transaction in a database system is described in U.S. patent application Ser. No. 10/364,065 filed by Amit Ganesh, et al. on Feb. 10, 2003, entitled “Method And Mechanism For Rolling Back A Transaction On A Row of Data”, the contents of which is incorporated by this reference in its entirety for all purposes as if fully set forth herein.
- A related technique, for handling a “flashback cursor” that is created in response to receipt of a “flashback query” and that is a particular type of cursor that is used to access past data is described in U.S. patent application Ser. No. 10/325,211 filed by Bipul Sinha, et al. on Dec. 18, 2002, entitled “Method And Apparatus For Accessing Data As It Existed At A Previous Point In Time”, the contents of which is incorporated by this reference in its entirety for all purposes as if fully set forth herein.
- In another incarnation, temporal access enables a user to query particular data over a range of time, rather than at a point in time. A user can query and manipulate multiple versions of data at the row level. Hence, the reach of the temporal access evolved from accessing the state of data at a point in time to the progression of data over a span of time. For example, in response to a “version” query, transaction metadata is returned for transactions that occurred on the specified data over the specified range of time, such as metadata that identifies what transactions were committed and when. Using this technology, one can pinpoint when and how data is changed and trace it back to the user, application, or transaction that changed the data.
- Available techniques for implementing row versioning, which enables accessing and manipulating multiple versions of a row of a database table, including one or more past versions, are described in U.S. Provisional Patent Application No. 60/500,509, entitled “System, Structure, Interface, and Semantics For Implementing Row Versions: Accessing Past Versions Of A Data Item” and U.S. Provisional Patent Application No. 60/500,510, entitled “Method and Mechanism For Row Versioning”.
- The current state of temporal database access is extended to provide fast and easy recovery at the database, table, row, and transaction level, and by just operating on the changed data. Therefore, data can be queried as it existed in the past, current data can be compared to past data, and deleted or changed data can be recovered. The time it takes to recover from an error is now equal to the amount of time it took to make the error. However, even in light of the existing capabilities regarding temporal access to data in a database, and the benefits provided thereby, there is room for improvement in methods for temporal access to data.
- Embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
-
FIG. 1 is a block diagram that illustrates an operating environment in which an embodiment of the invention may be implemented; -
FIG. 2 is a flow diagram that illustrates a method for managing requests for data, according to an embodiment of the invention; and -
FIG. 3 is a block diagram that illustrates a computer system upon which an embodiment of the invention may be implemented. - In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent, however, that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring embodiments of the present invention.
- Functional Overview of Embodiments
- Techniques are provided for querying past versions of data in a distributed database system that has multiple databases and associated database servers. Using temporal database access mechanisms, a request for data, in a past state, from a “remote” database, can be received at a “local” database server. Relevant portions of the request are passed to the remote server, where the relevant portions are processed. The processing performed by the remote server includes returning the requested data in the specified past state to the local server, or at least returning enough information to reconstruct the data into the past state. In this context, “local” simply refers to the database server that receives the request, e.g., a database query, from a user; and “remote” simply refers to another database and/or server that is associated with the local server via a conventional distributed database link.
- A request for a past version of data includes a time-specifying parameter to specify the past version of the data, which may include a timestamp, a system change number that is used to track the sequence in which events occur within a database server, and the like. Furthermore, the time-specifying parameter may include a time interval with which the data is associated in the remote database, where multiple versions of the data are returned, or at least enough information to reconstruct the data into the past versions, each of which is associated with a time that falls within the time interval.
- Examples of the breadth of applicability of these techniques include application (1) to a distributed database system comprising many databases, (2) to database query operations on the past version of the data, (3) to database query operations on the past version of the data and a current version of the same or other data, from the same or another database, and (4) to database query operations on the past version of the data and the same or other data in a different past state, from the same or another database.
- Operating Environment
-
FIG. 1 is a block diagram that illustrates an operating environment in which an embodiment of the invention may be implemented. The operating environment ofFIG. 1 is referred to herein as a distributed database system (or, simply, a distributed database). Generally, a distributed database comprises a set of databases, each stored on different storage mechanisms, that appears to applications as a single database. Consequently, an application can simultaneously access and modify the data in several databases in a network. Each database in the system is controlled by its local database management server (DBMS) but cooperates to maintain the consistency of the global distributed database. - Distributed
database 100 is illustrated as having three interconnected databases; however, a distributed database can generally comprise any number of interconnected databases. Thus,FIG. 3 depicts three databases simply for purposes of example and explanation. Distributeddatabase 100 comprises a number of database servers (“server”) 102 a, 102 b, 102 c that are each communicatively connected torespective databases servers more network 106, such as a conventional LAN (Local Area Network), a WAN (Wide Area Network) such as the Internet, or both. Through thenetwork 106 connections, the servers can exchange database statements such as standard SQL queries or portions thereof, and/or portions of a query execution plan. - A
database server database - Although not depicted in
FIG. 1 , eachdatabase server database 100 is communicatively connected to one or more client applications via one or more networks, such as a conventional LAN or WAN. The network(s) that connects client applications to the database servers may or may not be the same asnetwork 106, which interconnects the database servers. Client applications are typically software programs that request and possibly manipulate data, via adatabase server databases - Each
server computer system 300 ofFIG. 3 . A server in a distributed database system can act as a client, a server, or both. For example, theserver 102 a used to managedatabase 104 a is acting as a server when a statement is issued against its local data indatabase 104 a, and is acting as a client when it issues a statement against remote data indatabase 104 b. - Each
database - Each
database database 100 is distinct from all other databases in the system. Each database of a distributed database typically stores different data than the other databases in the system, i.e., the different databases are not simply back-ups of another database. For example, eachdatabase - To facilitate client requests in distributed
database 100,servers server 102 a is associated with a database link 108 ab that points toserver 102 b and, similarly,server 102 b is associated with a database link 108 ba that points toserver 102 a. Similarly,servers servers - Once a database link is created, client applications connected to a local database can access data in a remote database via the associated database link. A database link may be a private database link in a specific schema of a local database, with which only the owner of the private database link or subprograms in the schema can use the private database link to access data and database objects in the corresponding remote database. A database link may be a public database link, with which all users and subprograms in the local database can use the public database link to access data and database objects in the corresponding remote database.
- A distributed database typically supports (1) remote queries, updates, and transactions which select or update information from one or more remote tables, all of which reside at the same remote node; (2) distributed queries, updates, and transactions, which select or update information from two or more nodes, each of which may be a local or a remote node. Client applications of a distributed database can make local procedure calls to perform work at a local database and remote procedure calls to perform work at a remote database, through which the local server passes all procedure parameters in the call to the remote server.
- Location transparency within a distributed database exists when a user can universally refer to a database object, such as a table, regardless of the node to which an application connects. Synonyms can be used to establish location transparency for the tables and supporting objects in an application schema, where synonyms are created in a local database for tables in a remote database. Consequently, rather than accessing a remote table using its actual database link path to the table, the remote table can be accessed using a much simpler query, using the synonym, that does not have to account for the table location. Through use of location transparency, query, update and transaction transparency is also provided by a distributed database such as distributed
database 100. - Processing Requests for Past Versions of Data in a Distributed Database
-
FIG. 2 is a flow diagram that illustrates a method for managing requests for data, according to an embodiment of the invention. In the context of a database, the illustrated method is performed by, for example, a database management server such as any ofservers - At
block 202, a request is received at a first database server that manages a first database, where the request is for a past version of data that is stored in a second database that is managed by a second database server. The data is stored in a current state in the second database. The requested data is not also stored in the first database, such as in a redundant database architecture. However, the second database also stores enough information, such as metadata and transaction log files (e.g., undo and redo files), to reconstruct the past version of the data. For example, a request is received atdatabase server 102 a, via a network, from a user working at a web browser, where the request is for a past version of data that is stored indatabase 104 b. - The database server that receives the original request from the client is referred to herein as the “local” server and the database managed by the local server is referred to herein as the “local” database; whereas any of the other database servers and databases in the distributed database system other than the local server and database are referred to herein as a “remote” server and a “remote” database, respectively.
- The past version of data that is requested at
block 202 is specified, in one embodiment, by a time-specifying parameter within the request. In one implementation, the time-specifying parameter may specify a particular time that can be compared to a timestamp that is associated with the requested past version of data, and in another implementation, the time-specifying parameter may be a system change number (SCN) associated with a transaction on the requested data. In either case, the request specifies a point in time that can be used by the remote server to identify the past version of the data. The remote database in which the requested data is stored is specified in the request, by specifying the requested data in association with the relevant database link, or by specifying the requested data in conjunction with a synonym for the table that contains the data at the database link. - In one embodiment, the request received at
block 202 specifies a time interval with which the data is associated in the second database. If there were multiple versions of the data during that time interval, then the request is for each of the multiple versions. What data is returned in response to this type of request is described in reference to block 206. - With use of various techniques that are described in the related and otherwise herein-referenced patents and patent applications, a multiplicity of data request types can be made. For non-limiting examples, in conjunction with a request for a past version of data stored in a remote database, a query can be submitted to a database server that includes (1) a request for a current version of the same data represented in the requested past version, from the same remote database; (2) a request for a past version of different data from the same remote database; (3) a request for a past version of different data from a different database in the distributed database system, whether it be the local database or a different remote database; (4) a request for a current version of different data from a different database in the distributed database system, whether it be the local database or a different remote database; (5) a request for multiple past versions of the same data, at different points or intervals in time, from the same remote database; (6) a request for multiple past versions of different data, at the same or different points or intervals in time, from other database(s) in the distributed database system, whether it be from the local database or different remote databases; and the like.
- Furthermore, the request received at
block 202 may also specify a database operation to perform on the past data, such as a join of (a) a table that contains the past version of the data, with (b) a table that contains a past or current version of the same or other data; or may specify a past version of data in a subquery clause of a DML (data manipulation language) operation or DDL (data definition language) operation. - At
block 204, the past version of the data is requested from the second database server, in response to the request received atblock 202. For example,local database server 102 a passes a portion of the query, or a portion of the query execution plan, toremote database server 102 b for retrieval of the requested past version of data fromdatabase 104 b. - For example, in generation of a query execution plan by a query optimizer program at the
local server 102 a, the optimizer recognizes that the query contains a request for data from a linkedremote database 104 b, and causes at least a portion of the query or query plan which is relevant to the requested data to be passed to theremote server 102 b, where the portion is executed.Local server 102 a passes the portion toserver 102 b via thenetwork 106. One technique for passing information that specifies the requested point or interval in time to theremote server 102 b is to pass the information to an API associated with the remote server, where the API allows the passing of and is able to handle such information. One other technique for passing such information to theremote server 102 b is to pass the information using a remote procedure call to a procedure that executes on the remote server. Use of the technique described is not limited to any particular approach to passing the time-specifying information from the local server to the remote server. - At
block 206, the past version of the data is received at the first (i.e., local) database server from the second (i.e., remote) database server. Execution of the portion of the query or plan that was passed to the remote server atblock 204, which is performed at the remote server, may vary from implementation to implementation. For example, what is performed at the remote server may entail simply accessing and returning to the local server the data and relevant metadata that can be used to reconstruct the past version of the data, or actually reconstructing the past version of the data. Hence, the past version of the data that is received at the local server atblock 206 may comprise the data and relevant metadata that can be used to reconstruct the past version of the data by the local server, or a complete reconstructed past version of the data. - The technique described allows a user to see the data in the past state without persistently transforming the data. Furthermore, a user can simply request the past version of data using a query represented in a conventional query language, such as SQL, without requiring the expertise of a database administrator.
- With the embodiment in which the request for a past version of data specifies a time interval with which the data is associated in the second database, block 206 comprises receiving multiple versions of the data, each of which is associated with a time that falls within the specified time interval. For example, what is received at the local server may be a past version and a current version of the data if the specified time interval ends with a current time (e.g., a time after which no transactions have committed changes on the requested data), or may be multiple past versions that are associated with respective database transactions that were committed on the requested data during the specified time interval.
- In one related embodiment, at
block 206, transaction metadata is received at the local server from the remote server, where the transaction metadata includes information that describes what database transactions were committed on the data during the specified time interval and when the transactions committed, which can be used to reconstruct the various versions of the data that existed at times within the time interval. This allows a user to see the progression of the data over the time interval. - In summary, the method described in reference to
FIG. 2 provides for querying, from a local server in a distributed database system, past versions of data from a remote server in the distributed database system, using temporal database access mechanisms. - Hardware Overview
-
FIG. 3 is a block diagram that illustrates acomputer system 300 upon which an embodiment of the invention may be implemented.Computer system 300 includes abus 302 or other communication mechanism for communicating information, and aprocessor 304 coupled withbus 302 for processing information.Computer system 300 also includes amain memory 306, such as a random access memory (RAM) or other dynamic storage device, coupled tobus 302 for storing information and instructions to be executed byprocessor 304.Main memory 306 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed byprocessor 304.Computer system 300 further includes a read only memory (ROM) 308 or other static storage device coupled tobus 302 for storing static information and instructions forprocessor 304. Astorage device 310, such as a magnetic disk, optical disk, or magneto-optical disk, is provided and coupled tobus 302 for storing information and instructions. -
Computer system 300 may be coupled viabus 302 to adisplay 312, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), for displaying information to a computer user. Aninput device 314, including alphanumeric and other keys, is coupled tobus 302 for communicating information and command selections toprocessor 304. Another type of user input device iscursor control 316, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections toprocessor 304 and for controlling cursor movement ondisplay 312. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. - The invention is related to the use of
computer system 300 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed bycomputer system 300 in response toprocessor 304 executing one or more sequences of one or more instructions contained inmain memory 306. Such instructions may be read intomain memory 306 from another computer-readable medium, such asstorage device 310. Execution of the sequences of instructions contained inmain memory 306 causesprocessor 304 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software. - The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to
processor 304 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic, or magneto-optical disks, such asstorage device 310. Volatile media includes dynamic memory, such asmain memory 306. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprisebus 302. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. - Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
- Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to
processor 304 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local tocomputer system 300 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data onbus 302.Bus 302 carries the data tomain memory 306, from whichprocessor 304 retrieves and executes the instructions. The instructions received bymain memory 306 may optionally be stored onstorage device 310 either before or after execution byprocessor 304. -
Computer system 300 also includes acommunication interface 318 coupled tobus 302.Communication interface 318 provides a two-way data communication coupling to anetwork link 320 that is connected to alocal network 322. For example,communication interface 318 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example,communication interface 318 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation,communication interface 318 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information. - Network link 320 typically provides data communication through one or more networks to other data devices. For example,
network link 320 may provide a connection throughlocal network 322 to ahost computer 324 or to data equipment operated by an Internet Service Provider (ISP) 326.ISP 326 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 328.Local network 322 andInternet 328 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals onnetwork link 320 and throughcommunication interface 318, which carry the digital data to and fromcomputer system 300, are exemplary forms of carrier waves transporting the information. -
Computer system 300 can send messages and receive data, including program code, through the network(s),network link 320 andcommunication interface 318. In the Internet example, aserver 330 might transmit a requested code for an application program throughInternet 328,ISP 326,local network 322 andcommunication interface 318. - The received code may be executed by
processor 304 as it is received, and/or stored instorage device 310, or other non-volatile storage for later execution. In this manner,computer system 300 may obtain application code in the form of a carrier wave. - Extensions and Alternatives
- Alternative embodiments of the invention are described throughout the foregoing description, and in locations that best facilitate understanding the context of the embodiments. Furthermore, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. Therefore, the specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
- In addition, in this description certain process steps are set forth in a particular order, and alphabetic and alphanumeric labels may be used to identify certain steps. Unless specifically stated in the description, embodiments of the invention are not necessarily limited to any particular order of carrying out such steps. In particular, the labels are used merely for convenient identification of steps, and are not intended to specify or require a particular order of carrying out such steps.
Claims (35)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/866,333 US7552149B2 (en) | 2003-09-06 | 2004-06-10 | Querying past versions of data in a distributed database |
US14/609,265 US10509773B2 (en) | 2004-06-10 | 2015-01-29 | DBFS with flashback archive |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US50050903P | 2003-09-06 | 2003-09-06 | |
US50051003P | 2003-09-06 | 2003-09-06 | |
US57076904P | 2004-05-12 | 2004-05-12 | |
US10/866,333 US7552149B2 (en) | 2003-09-06 | 2004-06-10 | Querying past versions of data in a distributed database |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050055385A1 true US20050055385A1 (en) | 2005-03-10 |
US7552149B2 US7552149B2 (en) | 2009-06-23 |
Family
ID=34229432
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/866,333 Active 2025-08-27 US7552149B2 (en) | 2003-09-06 | 2004-06-10 | Querying past versions of data in a distributed database |
Country Status (1)
Country | Link |
---|---|
US (1) | US7552149B2 (en) |
Cited By (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020116176A1 (en) * | 2000-04-20 | 2002-08-22 | Valery Tsourikov | Semantic answering system and method |
US20040153441A1 (en) * | 2003-01-30 | 2004-08-05 | International Business Machines Coporation | Method of synchronizing distributed but interconnected data repositories |
US20050278350A1 (en) * | 2004-05-27 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values |
US20050278359A1 (en) * | 2004-06-10 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values in a multinode system |
US6983286B1 (en) * | 2002-05-10 | 2006-01-03 | Oracle International Corporation | Method and apparatus for accessing data as it existed at a previous point in time |
US20060020594A1 (en) * | 2004-07-21 | 2006-01-26 | Microsoft Corporation | Hierarchical drift detection of data sets |
US20060041424A1 (en) * | 2001-07-31 | 2006-02-23 | James Todhunter | Semantic processor for recognition of cause-effect relations in natural language documents |
US20060149707A1 (en) * | 2004-12-30 | 2006-07-06 | Mitchell Mark A | Multiple active database systems |
US20070088912A1 (en) * | 2005-10-05 | 2007-04-19 | Oracle International Corporation | Method and system for log structured relational database objects |
US20070094237A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Multiple active database systems |
US20070094238A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Transfering database workload among multiple database systems |
US20070094308A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Maintaining synchronization among multiple active database systems |
US20070136383A1 (en) * | 2005-12-13 | 2007-06-14 | International Business Machines Corporation | Database Tuning Method and System |
US20070156393A1 (en) * | 2001-07-31 | 2007-07-05 | Invention Machine Corporation | Semantic processor for recognition of whole-part relations in natural language documents |
US20070174349A1 (en) * | 2004-12-30 | 2007-07-26 | Ncr Corporation | Maintaining consistent state information among multiple active database systems |
US20070208753A1 (en) * | 2004-12-30 | 2007-09-06 | Ncr Corporation | Routing database requests among multiple active database systems |
US20080016080A1 (en) * | 2006-07-12 | 2008-01-17 | International Business Machines Corporation | System and method for virtualization of relational stored procedures in non-native relational database systems |
US20080027902A1 (en) * | 2006-07-26 | 2008-01-31 | Elliott Dale N | Method and apparatus for selecting data records from versioned data |
US7353231B1 (en) * | 2005-10-21 | 2008-04-01 | At&T Corp. | Flip-flap mechanism for high availability, online analytical processing databases |
WO2008043392A1 (en) | 2006-10-10 | 2008-04-17 | Richard Chappuis | Information processing method |
US20080098045A1 (en) * | 2006-10-20 | 2008-04-24 | Oracle International Corporation | Techniques for automatically tracking and archiving transactional data changes |
US20080243801A1 (en) * | 2007-03-27 | 2008-10-02 | James Todhunter | System and method for model element identification |
US20080249990A1 (en) * | 2007-04-05 | 2008-10-09 | Oracle International Corporation | Accessing data from asynchronously maintained index |
US7457791B1 (en) | 2003-05-30 | 2008-11-25 | Microsoft Corporation | Using invariants to validate applications states |
US20080313207A1 (en) * | 2007-06-13 | 2008-12-18 | Chad Modad | System and method for collection, retrieval, and distribution of data |
US7484096B1 (en) | 2003-05-28 | 2009-01-27 | Microsoft Corporation | Data validation using signatures and sampling |
US20090055440A1 (en) * | 2007-08-21 | 2009-02-26 | Tetsuya Uemura | Information Update Method and Information Update System |
US7552149B2 (en) | 2003-09-06 | 2009-06-23 | Oracle International Corporation | Querying past versions of data in a distributed database |
US20090248717A1 (en) * | 2008-03-28 | 2009-10-01 | Oracle International Corporation | Temporal class loader |
US20100082529A1 (en) * | 2008-05-08 | 2010-04-01 | Riverbed Technology, Inc. | Log Structured Content Addressable Deduplicating Storage |
US20100235165A1 (en) * | 2009-03-13 | 2010-09-16 | Invention Machine Corporation | System and method for automatic semantic labeling of natural language texts |
US20100235340A1 (en) * | 2009-03-13 | 2010-09-16 | Invention Machine Corporation | System and method for knowledge research |
US7886124B2 (en) | 2007-07-30 | 2011-02-08 | Oracle International Corporation | Method and mechanism for implementing dynamic space management for large objects |
US20110184831A1 (en) * | 2008-06-02 | 2011-07-28 | Andrew Robert Dalgleish | An item recommendation system |
US8095827B2 (en) | 2007-11-16 | 2012-01-10 | International Business Machines Corporation | Replication management with undo and redo capabilities |
WO2012048151A2 (en) * | 2010-10-06 | 2012-04-12 | Jackson John D | Network-based communication, collaboration, and documentation |
US8352450B1 (en) | 2007-04-19 | 2013-01-08 | Owl Computing Technologies, Inc. | Database update through a one-way data link |
US20130151560A1 (en) * | 2010-07-12 | 2013-06-13 | Sap Ag | Systems and Methods for Secure Access of Data |
US20140025995A1 (en) * | 2012-07-19 | 2014-01-23 | Dell Products L.P. | Large log file diagnostics system |
WO2014035879A3 (en) * | 2012-08-30 | 2014-05-08 | Ozgun Ali Erdogan | Operating a distributed database with foreign tables |
CN103838745A (en) * | 2012-11-22 | 2014-06-04 | 腾讯科技(深圳)有限公司 | Processing method and device of webpage pre-reading |
US9575987B2 (en) | 2014-06-23 | 2017-02-21 | Owl Computing Technologies, Inc. | System and method for providing assured database updates via a one-way data link |
US9940660B2 (en) | 2013-06-27 | 2018-04-10 | Wal-Mart Stores, Inc. | Add items from previous orders |
US20180246948A1 (en) * | 2017-02-28 | 2018-08-30 | Sap Se | Replay of Redo Log Records in Persistency or Main Memory of Database Systems |
CN111869165A (en) * | 2018-01-22 | 2020-10-30 | 西门子股份公司 | Method and control system for controlling and/or monitoring a device |
US11238020B2 (en) | 2019-09-30 | 2022-02-01 | EMC IP Holding Company LLC | Maintaining temporal associations for event data in an event database |
US20220046110A1 (en) * | 2020-08-05 | 2022-02-10 | Salesforce.Com, Inc. | Virtual dataset management database system |
US20220398232A1 (en) * | 2021-06-14 | 2022-12-15 | Microsoft Technology Licensing, Llc | Versioned metadata using virtual databases |
CN117033398A (en) * | 2023-10-09 | 2023-11-10 | 之江实验室 | Data flashback query method and device based on dolt database |
US20230401186A1 (en) * | 2022-06-14 | 2023-12-14 | Maplebear Inc. (Dba Instacart) | Generating datastore checkpoints |
US11941074B2 (en) | 2022-03-18 | 2024-03-26 | International Business Machines Corporation | Fetching a query result using a query filter |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8290966B2 (en) * | 2007-11-29 | 2012-10-16 | Sap Aktiengesellschaft | System and method for implementing a non-destructive tree filter |
US8818934B2 (en) * | 2008-03-13 | 2014-08-26 | Oracle International Corporation | Transparent support for distributed transactions in a clustered disk-sharing database environment |
Citations (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5212788A (en) * | 1990-05-22 | 1993-05-18 | Digital Equipment Corporation | System and method for consistent timestamping in distributed computer databases |
US5280612A (en) * | 1991-11-26 | 1994-01-18 | International Business Machines Corporation | Multiple version database concurrency control system |
US5317731A (en) * | 1991-02-25 | 1994-05-31 | International Business Machines Corporation | Intelligent page store for concurrent and consistent access to a database by a transaction processor and a query processor |
US5333316A (en) * | 1991-08-16 | 1994-07-26 | International Business Machines Corporation | Locking and row by row modification of a database stored in a single master table and multiple virtual tables of a plurality of concurrent users |
US5347653A (en) * | 1991-06-28 | 1994-09-13 | Digital Equipment Corporation | System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes |
US5440730A (en) * | 1990-08-09 | 1995-08-08 | Bell Communications Research, Inc. | Time index access structure for temporal databases having concurrent multiple versions |
US5447164A (en) * | 1993-11-08 | 1995-09-05 | Hewlett-Packard Company | Interactive medical information display system and method for displaying user-definable patient events |
US5452445A (en) * | 1992-04-30 | 1995-09-19 | Oracle Corporation | Two-pass multi-version read consistency |
US5613113A (en) * | 1993-10-08 | 1997-03-18 | International Business Machines Corporation | Consistent recreation of events from activity logs |
US5638508A (en) * | 1987-07-17 | 1997-06-10 | Hitachi, Ltd. | Method and a system for processing a log record |
US5701480A (en) * | 1991-10-17 | 1997-12-23 | Digital Equipment Corporation | Distributed multi-version commitment ordering protocols for guaranteeing serializability during transaction processing |
US5857204A (en) * | 1996-07-02 | 1999-01-05 | Ab Initio Software Corporation | Restoring the state of a set of files |
US5870758A (en) * | 1996-03-11 | 1999-02-09 | Oracle Corporation | Method and apparatus for providing isolation levels in a database system |
US5873102A (en) * | 1997-04-29 | 1999-02-16 | Oracle Corporation | Pluggable tablespaces on a transportable medium |
US5890167A (en) * | 1997-05-08 | 1999-03-30 | Oracle Corporation | Pluggable tablespaces for database systems |
US5907848A (en) * | 1997-03-14 | 1999-05-25 | Lakeview Technology, Inc. | Method and system for defining transactions from a database log |
US5930794A (en) * | 1996-10-18 | 1999-07-27 | Sagent Technologies, Inc. | Database repository with deferred transactions |
US5956731A (en) * | 1997-04-23 | 1999-09-21 | Oracle Corporation | Sharing snapshots for consistent reads |
US5974427A (en) * | 1993-12-15 | 1999-10-26 | Microsoft Corporation | Method and computer system for implementing concurrent accesses of a database record by multiple users |
US5999924A (en) * | 1997-07-25 | 1999-12-07 | Amazon.Com, Inc. | Method and apparatus for producing sequenced queries |
US6012059A (en) * | 1997-08-21 | 2000-01-04 | Dataxel Corporation | Method and apparatus for replicated transaction consistency |
US6012060A (en) * | 1997-05-30 | 2000-01-04 | Oracle Corporation | Sharing, updating data blocks among multiple nodes in a distributed system |
US6014674A (en) * | 1996-11-14 | 2000-01-11 | Sybase, Inc. | Method for maintaining log compatibility in database systems |
US6018746A (en) * | 1997-12-23 | 2000-01-25 | Unisys Corporation | System and method for managing recovery information in a transaction processing system |
US6029160A (en) * | 1995-05-24 | 2000-02-22 | International Business Machines Corporation | Method and means for linking a database system with a system for filing data |
US6067550A (en) * | 1997-03-10 | 2000-05-23 | Microsoft Corporation | Database computer system with application recovery and dependency handling write cache |
US6138121A (en) * | 1998-05-29 | 2000-10-24 | Hewlett-Packard Company | Network management event storage and manipulation using relational database technology in a data warehouse |
US6173292B1 (en) * | 1998-03-04 | 2001-01-09 | International Business Machines Corporation | Data recovery in a transactional database using write-ahead logging and file caching |
US6182241B1 (en) * | 1996-03-19 | 2001-01-30 | Oracle Corporation | Method and apparatus for improved transaction recovery |
US6192377B1 (en) * | 1998-05-13 | 2001-02-20 | Oracle Corporation | Method and apparatus for determing whether a transaction can use a version of a data item |
US6192378B1 (en) * | 1998-05-13 | 2001-02-20 | International Business Machines Corporation | Method and apparatus for combining undo and redo contexts in a distributed access environment |
US6237001B1 (en) * | 1997-04-23 | 2001-05-22 | Oracle Corporation | Managing access to data in a distributed database environment |
US6243702B1 (en) * | 1998-06-22 | 2001-06-05 | Oracle Corporation | Method and apparatus for propagating commit times between a plurality of database servers |
US6263338B1 (en) * | 1997-07-21 | 2001-07-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Method relating to databases |
US6321324B1 (en) * | 1995-04-28 | 2001-11-20 | Sgs-Thomson Microelectronics S.A. | Device for putting an integrated circuit into operation |
US6345268B1 (en) * | 1997-06-09 | 2002-02-05 | Carlos De La Huerga | Method and system for resolving temporal descriptors of data records in a computer system |
US20020116457A1 (en) * | 2001-02-22 | 2002-08-22 | John Eshleman | Systems and methods for managing distributed database resources |
US6449624B1 (en) * | 1999-10-18 | 2002-09-10 | Fisher-Rosemount Systems, Inc. | Version control and audit trail in a process control system |
US6502133B1 (en) * | 1999-03-25 | 2002-12-31 | Lucent Technologies Inc. | Real-time event processing system with analysis engine using recovery information |
US6505228B1 (en) * | 1998-07-22 | 2003-01-07 | Cisco Technology, Inc. | Dynamic determination of execution sequence |
US6567928B1 (en) * | 2000-05-23 | 2003-05-20 | International Business Machines Corporation | Method and apparatus for efficiently recovering from a failure in a database that includes unlogged objects |
US6609123B1 (en) * | 1999-09-03 | 2003-08-19 | Cognos Incorporated | Query engine and method for querying data using metadata model |
US6618822B1 (en) * | 2000-01-03 | 2003-09-09 | Oracle International Corporation | Method and mechanism for relational access of recovery logs in a database system |
US6631374B1 (en) * | 2000-09-29 | 2003-10-07 | Oracle Corp. | System and method for providing fine-grained temporal database access |
US6647473B1 (en) * | 2000-02-16 | 2003-11-11 | Microsoft Corporation | Kernel-based crash-consistency coordinator |
US6647510B1 (en) * | 1996-03-19 | 2003-11-11 | Oracle International Corporation | Method and apparatus for making available data that was locked by a dead transaction before rolling back the entire dead transaction |
US6681230B1 (en) * | 1999-03-25 | 2004-01-20 | Lucent Technologies Inc. | Real-time event processing system with service authoring environment |
US6714943B1 (en) * | 2001-01-31 | 2004-03-30 | Oracle International Corporation | Method and mechanism for tracking dependencies for referential integrity constrained tables |
US6735605B2 (en) * | 2000-06-02 | 2004-05-11 | International Business Machines Corporation | Method and apparatus for synchronizing not-logged application temporary tables in a multi-node relational database management system |
US6738975B1 (en) * | 1998-11-18 | 2004-05-18 | Software Ag, Inc. | Extensible distributed enterprise application integration system |
US6769074B2 (en) * | 2000-05-25 | 2004-07-27 | Lumigent Technologies, Inc. | System and method for transaction-selective rollback reconstruction of database objects |
US6769124B1 (en) * | 1998-07-22 | 2004-07-27 | Cisco Technology, Inc. | Persistent storage of information objects |
US20050055603A1 (en) * | 2003-08-14 | 2005-03-10 | Soran Philip E. | Virtual disk drive system and method |
US20050144199A2 (en) * | 2002-05-31 | 2005-06-30 | Lefthand Networks, Inc. | Distributed Network Storage System With Virtualization |
US20050256897A1 (en) * | 2004-05-11 | 2005-11-17 | Oracle International Corporation | Providing the timing of the last committed change to a row in a database table |
US20050278350A1 (en) * | 2004-05-27 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values |
US7237075B2 (en) * | 2002-01-22 | 2007-06-26 | Columbia Data Products, Inc. | Persistent snapshot methods |
US7274783B2 (en) * | 2000-02-15 | 2007-09-25 | Nortel Networks Limited | Methods and systems for implementing a real-time, distributed, hierarchical database using a proxiable protocol |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2746526B1 (en) | 1996-03-25 | 1998-06-05 | Digital Equipment Corp | METHOD FOR CONSERVING A DATABASE WITH TEMPORAL AND SPATIAL ORGANIZATION |
US7552149B2 (en) | 2003-09-06 | 2009-06-23 | Oracle International Corporation | Querying past versions of data in a distributed database |
-
2004
- 2004-06-10 US US10/866,333 patent/US7552149B2/en active Active
Patent Citations (62)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5638508A (en) * | 1987-07-17 | 1997-06-10 | Hitachi, Ltd. | Method and a system for processing a log record |
US5212788A (en) * | 1990-05-22 | 1993-05-18 | Digital Equipment Corporation | System and method for consistent timestamping in distributed computer databases |
US5440730A (en) * | 1990-08-09 | 1995-08-08 | Bell Communications Research, Inc. | Time index access structure for temporal databases having concurrent multiple versions |
US5317731A (en) * | 1991-02-25 | 1994-05-31 | International Business Machines Corporation | Intelligent page store for concurrent and consistent access to a database by a transaction processor and a query processor |
US5347653A (en) * | 1991-06-28 | 1994-09-13 | Digital Equipment Corporation | System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes |
US5333316A (en) * | 1991-08-16 | 1994-07-26 | International Business Machines Corporation | Locking and row by row modification of a database stored in a single master table and multiple virtual tables of a plurality of concurrent users |
US5701480A (en) * | 1991-10-17 | 1997-12-23 | Digital Equipment Corporation | Distributed multi-version commitment ordering protocols for guaranteeing serializability during transaction processing |
US5280612A (en) * | 1991-11-26 | 1994-01-18 | International Business Machines Corporation | Multiple version database concurrency control system |
US5452445A (en) * | 1992-04-30 | 1995-09-19 | Oracle Corporation | Two-pass multi-version read consistency |
US5613113A (en) * | 1993-10-08 | 1997-03-18 | International Business Machines Corporation | Consistent recreation of events from activity logs |
US5447164A (en) * | 1993-11-08 | 1995-09-05 | Hewlett-Packard Company | Interactive medical information display system and method for displaying user-definable patient events |
US5974427A (en) * | 1993-12-15 | 1999-10-26 | Microsoft Corporation | Method and computer system for implementing concurrent accesses of a database record by multiple users |
US6321324B1 (en) * | 1995-04-28 | 2001-11-20 | Sgs-Thomson Microelectronics S.A. | Device for putting an integrated circuit into operation |
US6029160A (en) * | 1995-05-24 | 2000-02-22 | International Business Machines Corporation | Method and means for linking a database system with a system for filing data |
US5870758A (en) * | 1996-03-11 | 1999-02-09 | Oracle Corporation | Method and apparatus for providing isolation levels in a database system |
US6182241B1 (en) * | 1996-03-19 | 2001-01-30 | Oracle Corporation | Method and apparatus for improved transaction recovery |
US6647510B1 (en) * | 1996-03-19 | 2003-11-11 | Oracle International Corporation | Method and apparatus for making available data that was locked by a dead transaction before rolling back the entire dead transaction |
US5857204A (en) * | 1996-07-02 | 1999-01-05 | Ab Initio Software Corporation | Restoring the state of a set of files |
US5930794A (en) * | 1996-10-18 | 1999-07-27 | Sagent Technologies, Inc. | Database repository with deferred transactions |
US6480847B1 (en) * | 1996-10-18 | 2002-11-12 | Sagent Technology, Inc. | Database repository with deferred transactions |
US6014674A (en) * | 1996-11-14 | 2000-01-11 | Sybase, Inc. | Method for maintaining log compatibility in database systems |
US6067550A (en) * | 1997-03-10 | 2000-05-23 | Microsoft Corporation | Database computer system with application recovery and dependency handling write cache |
US5907848A (en) * | 1997-03-14 | 1999-05-25 | Lakeview Technology, Inc. | Method and system for defining transactions from a database log |
US6237001B1 (en) * | 1997-04-23 | 2001-05-22 | Oracle Corporation | Managing access to data in a distributed database environment |
US5956731A (en) * | 1997-04-23 | 1999-09-21 | Oracle Corporation | Sharing snapshots for consistent reads |
US5873102A (en) * | 1997-04-29 | 1999-02-16 | Oracle Corporation | Pluggable tablespaces on a transportable medium |
US5890167A (en) * | 1997-05-08 | 1999-03-30 | Oracle Corporation | Pluggable tablespaces for database systems |
US6012060A (en) * | 1997-05-30 | 2000-01-04 | Oracle Corporation | Sharing, updating data blocks among multiple nodes in a distributed system |
US6345268B1 (en) * | 1997-06-09 | 2002-02-05 | Carlos De La Huerga | Method and system for resolving temporal descriptors of data records in a computer system |
US6263338B1 (en) * | 1997-07-21 | 2001-07-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Method relating to databases |
US6003024A (en) * | 1997-07-25 | 1999-12-14 | Amazon. Com | System and method for selecting rows from dimensional databases |
US6233573B1 (en) * | 1997-07-25 | 2001-05-15 | Amazon.Com, Inc. | System and method for selecting rows from dimensional databases having temporal dimention |
US5999924A (en) * | 1997-07-25 | 1999-12-07 | Amazon.Com, Inc. | Method and apparatus for producing sequenced queries |
US6012059A (en) * | 1997-08-21 | 2000-01-04 | Dataxel Corporation | Method and apparatus for replicated transaction consistency |
US6018746A (en) * | 1997-12-23 | 2000-01-25 | Unisys Corporation | System and method for managing recovery information in a transaction processing system |
US6173292B1 (en) * | 1998-03-04 | 2001-01-09 | International Business Machines Corporation | Data recovery in a transactional database using write-ahead logging and file caching |
US6192377B1 (en) * | 1998-05-13 | 2001-02-20 | Oracle Corporation | Method and apparatus for determing whether a transaction can use a version of a data item |
US6192378B1 (en) * | 1998-05-13 | 2001-02-20 | International Business Machines Corporation | Method and apparatus for combining undo and redo contexts in a distributed access environment |
US6138121A (en) * | 1998-05-29 | 2000-10-24 | Hewlett-Packard Company | Network management event storage and manipulation using relational database technology in a data warehouse |
US6636851B1 (en) * | 1998-06-22 | 2003-10-21 | Oracle International Corporation | Method and apparatus for propagating commit times between a plurality of database servers |
US6243702B1 (en) * | 1998-06-22 | 2001-06-05 | Oracle Corporation | Method and apparatus for propagating commit times between a plurality of database servers |
US6769124B1 (en) * | 1998-07-22 | 2004-07-27 | Cisco Technology, Inc. | Persistent storage of information objects |
US6505228B1 (en) * | 1998-07-22 | 2003-01-07 | Cisco Technology, Inc. | Dynamic determination of execution sequence |
US6738975B1 (en) * | 1998-11-18 | 2004-05-18 | Software Ag, Inc. | Extensible distributed enterprise application integration system |
US6502133B1 (en) * | 1999-03-25 | 2002-12-31 | Lucent Technologies Inc. | Real-time event processing system with analysis engine using recovery information |
US6681230B1 (en) * | 1999-03-25 | 2004-01-20 | Lucent Technologies Inc. | Real-time event processing system with service authoring environment |
US6609123B1 (en) * | 1999-09-03 | 2003-08-19 | Cognos Incorporated | Query engine and method for querying data using metadata model |
US6449624B1 (en) * | 1999-10-18 | 2002-09-10 | Fisher-Rosemount Systems, Inc. | Version control and audit trail in a process control system |
US6618822B1 (en) * | 2000-01-03 | 2003-09-09 | Oracle International Corporation | Method and mechanism for relational access of recovery logs in a database system |
US7274783B2 (en) * | 2000-02-15 | 2007-09-25 | Nortel Networks Limited | Methods and systems for implementing a real-time, distributed, hierarchical database using a proxiable protocol |
US6647473B1 (en) * | 2000-02-16 | 2003-11-11 | Microsoft Corporation | Kernel-based crash-consistency coordinator |
US6567928B1 (en) * | 2000-05-23 | 2003-05-20 | International Business Machines Corporation | Method and apparatus for efficiently recovering from a failure in a database that includes unlogged objects |
US6769074B2 (en) * | 2000-05-25 | 2004-07-27 | Lumigent Technologies, Inc. | System and method for transaction-selective rollback reconstruction of database objects |
US6735605B2 (en) * | 2000-06-02 | 2004-05-11 | International Business Machines Corporation | Method and apparatus for synchronizing not-logged application temporary tables in a multi-node relational database management system |
US6631374B1 (en) * | 2000-09-29 | 2003-10-07 | Oracle Corp. | System and method for providing fine-grained temporal database access |
US6714943B1 (en) * | 2001-01-31 | 2004-03-30 | Oracle International Corporation | Method and mechanism for tracking dependencies for referential integrity constrained tables |
US20020116457A1 (en) * | 2001-02-22 | 2002-08-22 | John Eshleman | Systems and methods for managing distributed database resources |
US7237075B2 (en) * | 2002-01-22 | 2007-06-26 | Columbia Data Products, Inc. | Persistent snapshot methods |
US20050144199A2 (en) * | 2002-05-31 | 2005-06-30 | Lefthand Networks, Inc. | Distributed Network Storage System With Virtualization |
US20050055603A1 (en) * | 2003-08-14 | 2005-03-10 | Soran Philip E. | Virtual disk drive system and method |
US20050256897A1 (en) * | 2004-05-11 | 2005-11-17 | Oracle International Corporation | Providing the timing of the last committed change to a row in a database table |
US20050278350A1 (en) * | 2004-05-27 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values |
Cited By (88)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7962326B2 (en) | 2000-04-20 | 2011-06-14 | Invention Machine Corporation | Semantic answering system and method |
US20020116176A1 (en) * | 2000-04-20 | 2002-08-22 | Valery Tsourikov | Semantic answering system and method |
US20070156393A1 (en) * | 2001-07-31 | 2007-07-05 | Invention Machine Corporation | Semantic processor for recognition of whole-part relations in natural language documents |
US9009590B2 (en) | 2001-07-31 | 2015-04-14 | Invention Machines Corporation | Semantic processor for recognition of cause-effect relations in natural language documents |
US20060041424A1 (en) * | 2001-07-31 | 2006-02-23 | James Todhunter | Semantic processor for recognition of cause-effect relations in natural language documents |
US8799776B2 (en) | 2001-07-31 | 2014-08-05 | Invention Machine Corporation | Semantic processor for recognition of whole-part relations in natural language documents |
US6983286B1 (en) * | 2002-05-10 | 2006-01-03 | Oracle International Corporation | Method and apparatus for accessing data as it existed at a previous point in time |
US20040153441A1 (en) * | 2003-01-30 | 2004-08-05 | International Business Machines Coporation | Method of synchronizing distributed but interconnected data repositories |
US7089232B2 (en) * | 2003-01-30 | 2006-08-08 | International Business Machines Corporation | Method of synchronizing distributed but interconnected data repositories |
US20090132955A1 (en) * | 2003-05-28 | 2009-05-21 | Microsoft Corporation | Data validation using signatures and sampling |
US20090125623A1 (en) * | 2003-05-28 | 2009-05-14 | Microsoft Corporation | Data validation using signatures and sampling |
US7966279B2 (en) | 2003-05-28 | 2011-06-21 | Microsoft Corporation | Data validation using signatures and sampling |
US8122253B2 (en) | 2003-05-28 | 2012-02-21 | Microsoft Corporation | Data validation using signatures and sampling |
US7484096B1 (en) | 2003-05-28 | 2009-01-27 | Microsoft Corporation | Data validation using signatures and sampling |
US8051288B2 (en) | 2003-05-28 | 2011-11-01 | Microsoft Corporation | Data validation using signatures and sampling |
US20090132461A1 (en) * | 2003-05-28 | 2009-05-21 | Microsoft Corporation | Data validation using signatures and sampling |
US7457791B1 (en) | 2003-05-30 | 2008-11-25 | Microsoft Corporation | Using invariants to validate applications states |
US7552149B2 (en) | 2003-09-06 | 2009-06-23 | Oracle International Corporation | Querying past versions of data in a distributed database |
US7240065B2 (en) | 2004-05-27 | 2007-07-03 | Oracle International Corporation | Providing mappings between logical time values and real time values |
US20050278350A1 (en) * | 2004-05-27 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values |
US7251660B2 (en) | 2004-06-10 | 2007-07-31 | Oracle International Corporation | Providing mappings between logical time values and real time values in a multinode system |
US20050278359A1 (en) * | 2004-06-10 | 2005-12-15 | Oracle International Corporation | Providing mappings between logical time values and real time values in a multinode system |
US20060020594A1 (en) * | 2004-07-21 | 2006-01-26 | Microsoft Corporation | Hierarchical drift detection of data sets |
US20070094238A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Transfering database workload among multiple database systems |
US20070174349A1 (en) * | 2004-12-30 | 2007-07-26 | Ncr Corporation | Maintaining consistent state information among multiple active database systems |
US20060149707A1 (en) * | 2004-12-30 | 2006-07-06 | Mitchell Mark A | Multiple active database systems |
US20070094237A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Multiple active database systems |
US20070094308A1 (en) * | 2004-12-30 | 2007-04-26 | Ncr Corporation | Maintaining synchronization among multiple active database systems |
US7567990B2 (en) | 2004-12-30 | 2009-07-28 | Teradata Us, Inc. | Transfering database workload among multiple database systems |
US20070208753A1 (en) * | 2004-12-30 | 2007-09-06 | Ncr Corporation | Routing database requests among multiple active database systems |
US20070088912A1 (en) * | 2005-10-05 | 2007-04-19 | Oracle International Corporation | Method and system for log structured relational database objects |
US7418544B2 (en) | 2005-10-05 | 2008-08-26 | Oracle International Corporation | Method and system for log structured relational database objects |
US7353231B1 (en) * | 2005-10-21 | 2008-04-01 | At&T Corp. | Flip-flap mechanism for high availability, online analytical processing databases |
US20070136383A1 (en) * | 2005-12-13 | 2007-06-14 | International Business Machines Corporation | Database Tuning Method and System |
US8180762B2 (en) * | 2005-12-13 | 2012-05-15 | International Business Machines Corporation | Database tuning methods |
US20080016080A1 (en) * | 2006-07-12 | 2008-01-17 | International Business Machines Corporation | System and method for virtualization of relational stored procedures in non-native relational database systems |
US7739296B2 (en) * | 2006-07-12 | 2010-06-15 | International Business Machines Corporation | System and method for virtualization of relational stored procedures in non-native relational database systems |
US20080027902A1 (en) * | 2006-07-26 | 2008-01-31 | Elliott Dale N | Method and apparatus for selecting data records from versioned data |
US7805439B2 (en) * | 2006-07-26 | 2010-09-28 | Intuit Inc. | Method and apparatus for selecting data records from versioned data |
US20090198665A1 (en) * | 2006-10-10 | 2009-08-06 | Richard Chappuis | Information processing method |
US8250039B2 (en) | 2006-10-10 | 2012-08-21 | Richard Chappuis | Information processing method |
WO2008043392A1 (en) | 2006-10-10 | 2008-04-17 | Richard Chappuis | Information processing method |
US8589357B2 (en) * | 2006-10-20 | 2013-11-19 | Oracle International Corporation | Techniques for automatically tracking and archiving transactional data changes |
US20080098045A1 (en) * | 2006-10-20 | 2008-04-24 | Oracle International Corporation | Techniques for automatically tracking and archiving transactional data changes |
US9031947B2 (en) * | 2007-03-27 | 2015-05-12 | Invention Machine Corporation | System and method for model element identification |
US20080243801A1 (en) * | 2007-03-27 | 2008-10-02 | James Todhunter | System and method for model element identification |
US7814117B2 (en) | 2007-04-05 | 2010-10-12 | Oracle International Corporation | Accessing data from asynchronously maintained index |
US20080249990A1 (en) * | 2007-04-05 | 2008-10-09 | Oracle International Corporation | Accessing data from asynchronously maintained index |
US8352450B1 (en) | 2007-04-19 | 2013-01-08 | Owl Computing Technologies, Inc. | Database update through a one-way data link |
US8819080B2 (en) * | 2007-06-13 | 2014-08-26 | The Boeing Company | System and method for collection, retrieval, and distribution of data |
US20080313207A1 (en) * | 2007-06-13 | 2008-12-18 | Chad Modad | System and method for collection, retrieval, and distribution of data |
US7886124B2 (en) | 2007-07-30 | 2011-02-08 | Oracle International Corporation | Method and mechanism for implementing dynamic space management for large objects |
US8073901B2 (en) * | 2007-08-21 | 2011-12-06 | Hitachi, Ltd. | Information update method and information update system |
US20090055440A1 (en) * | 2007-08-21 | 2009-02-26 | Tetsuya Uemura | Information Update Method and Information Update System |
US8095827B2 (en) | 2007-11-16 | 2012-01-10 | International Business Machines Corporation | Replication management with undo and redo capabilities |
US20090248717A1 (en) * | 2008-03-28 | 2009-10-01 | Oracle International Corporation | Temporal class loader |
US20100082529A1 (en) * | 2008-05-08 | 2010-04-01 | Riverbed Technology, Inc. | Log Structured Content Addressable Deduplicating Storage |
US9208031B2 (en) * | 2008-05-08 | 2015-12-08 | Riverbed Technology, Inc. | Log structured content addressable deduplicating storage |
US20110184831A1 (en) * | 2008-06-02 | 2011-07-28 | Andrew Robert Dalgleish | An item recommendation system |
US8666730B2 (en) | 2009-03-13 | 2014-03-04 | Invention Machine Corporation | Question-answering system and method based on semantic labeling of text documents and user questions |
US8583422B2 (en) | 2009-03-13 | 2013-11-12 | Invention Machine Corporation | System and method for automatic semantic labeling of natural language texts |
US8311999B2 (en) | 2009-03-13 | 2012-11-13 | Invention Machine Corporation | System and method for knowledge research |
US20100235165A1 (en) * | 2009-03-13 | 2010-09-16 | Invention Machine Corporation | System and method for automatic semantic labeling of natural language texts |
US20100235340A1 (en) * | 2009-03-13 | 2010-09-16 | Invention Machine Corporation | System and method for knowledge research |
US20130151560A1 (en) * | 2010-07-12 | 2013-06-13 | Sap Ag | Systems and Methods for Secure Access of Data |
US9002868B2 (en) * | 2010-07-12 | 2015-04-07 | Sap Se | Systems and methods for secure access of data |
WO2012048151A3 (en) * | 2010-10-06 | 2012-08-16 | Jackson John D | Network-based communication, collaboration, and documentation |
WO2012048151A2 (en) * | 2010-10-06 | 2012-04-12 | Jackson John D | Network-based communication, collaboration, and documentation |
US8977909B2 (en) * | 2012-07-19 | 2015-03-10 | Dell Products L.P. | Large log file diagnostics system |
US20140025995A1 (en) * | 2012-07-19 | 2014-01-23 | Dell Products L.P. | Large log file diagnostics system |
US9430316B2 (en) | 2012-07-19 | 2016-08-30 | Dell Products L.P. | Large log file diagnostics system |
US10489234B2 (en) | 2012-07-19 | 2019-11-26 | Dell Products L.P. | Large log file diagnostics system |
US10579634B2 (en) | 2012-08-30 | 2020-03-03 | Citus Data Bilgi Islemleri Ticaret A.S. | Apparatus and method for operating a distributed database with foreign tables |
WO2014035879A3 (en) * | 2012-08-30 | 2014-05-08 | Ozgun Ali Erdogan | Operating a distributed database with foreign tables |
CN103838745A (en) * | 2012-11-22 | 2014-06-04 | 腾讯科技(深圳)有限公司 | Processing method and device of webpage pre-reading |
US9940660B2 (en) | 2013-06-27 | 2018-04-10 | Wal-Mart Stores, Inc. | Add items from previous orders |
US10789636B2 (en) | 2013-06-27 | 2020-09-29 | Walmart Apollo, Llc | Add items from previous orders |
US9575987B2 (en) | 2014-06-23 | 2017-02-21 | Owl Computing Technologies, Inc. | System and method for providing assured database updates via a one-way data link |
US20180246948A1 (en) * | 2017-02-28 | 2018-08-30 | Sap Se | Replay of Redo Log Records in Persistency or Main Memory of Database Systems |
US11170023B2 (en) * | 2017-02-28 | 2021-11-09 | Sap Se | Replay of redo log records in persistency or main memory of database systems |
CN111869165A (en) * | 2018-01-22 | 2020-10-30 | 西门子股份公司 | Method and control system for controlling and/or monitoring a device |
US11231958B2 (en) | 2018-01-22 | 2022-01-25 | Siemens Aktiengesellschaft | Method and control system for controlling and/or monitoring devices |
US11238020B2 (en) | 2019-09-30 | 2022-02-01 | EMC IP Holding Company LLC | Maintaining temporal associations for event data in an event database |
US20220046110A1 (en) * | 2020-08-05 | 2022-02-10 | Salesforce.Com, Inc. | Virtual dataset management database system |
US20220398232A1 (en) * | 2021-06-14 | 2022-12-15 | Microsoft Technology Licensing, Llc | Versioned metadata using virtual databases |
US11941074B2 (en) | 2022-03-18 | 2024-03-26 | International Business Machines Corporation | Fetching a query result using a query filter |
US20230401186A1 (en) * | 2022-06-14 | 2023-12-14 | Maplebear Inc. (Dba Instacart) | Generating datastore checkpoints |
CN117033398A (en) * | 2023-10-09 | 2023-11-10 | 之江实验室 | Data flashback query method and device based on dolt database |
Also Published As
Publication number | Publication date |
---|---|
US7552149B2 (en) | 2009-06-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7552149B2 (en) | Querying past versions of data in a distributed database | |
US10635675B2 (en) | Supporting pluggable databases with heterogeneous database character sets in a container database | |
US8639677B2 (en) | Database replication techniques for maintaining original linear request order for asynchronous transactional events | |
US8612421B2 (en) | Efficient processing of relational joins of multidimensional data | |
US6067542A (en) | Pragma facility and SQL3 extension for optimal parallel UDF execution | |
US6502088B1 (en) | Method and system for improved access to non-relational databases | |
US6480848B1 (en) | Extension of data definition language (DDL) capabilities for relational databases for applications issuing DML and DDL statements | |
US8117174B2 (en) | Database system providing high performance database versioning | |
US11392588B2 (en) | Active queries filter extraction | |
US9411866B2 (en) | Replication mechanisms for database environments | |
US7769789B2 (en) | High performant row-level data manipulation using a data layer interface | |
US20060224626A1 (en) | Versioned file group repository | |
CA2484007C (en) | Providing a useable version of a data item | |
US6965899B1 (en) | Online reorganization and redefinition of relational database tables | |
US7953749B2 (en) | Providing the timing of the last committed change to a row in a database table | |
US20070185912A1 (en) | Off-loading I/O and computationally intensive operations to secondary systems | |
US9009101B2 (en) | Reducing contention of transaction logging in a database management system | |
US10509773B2 (en) | DBFS with flashback archive | |
US20040260690A1 (en) | Using multidimensional access as surrogate for run-time hash table | |
US7979412B2 (en) | Object query over previous query results | |
US7305422B1 (en) | Performing computationally intensive calculations within a database server that provides a recovery mechanism | |
US7415457B2 (en) | Using a cache to provide cursor isolation | |
US6453322B1 (en) | Extension of data definition language (DDL) capabilities for relational databases for applications issuing multiple units of work | |
US6421677B1 (en) | Extension of data definition language (DDL) capabilities for relational databases for applications issuing DDL statements | |
Hanson et al. | TriggerMan: An Asynchronous Trigger Processor as an Extension to an Object-Relational DBMS |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SINHA, BIPUL;GANESH, AMIT;REEL/FRAME:015465/0820 Effective date: 20040609 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |